Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add jepso-ci #32

Merged
merged 2 commits into from Jan 26, 2013
Merged

Add jepso-ci #32

merged 2 commits into from Jan 26, 2013

Conversation

ForbesLindesay
Copy link
Contributor

This P.R. will add jepso-ci to your repository. It lets you put a badge like:

build status

In the readme of your repository.

To enable jepso-ci just accept this pull request and then head over to settings/hooks select WebHookURLs and enter https://jepso-ci.com/api/hook then click Update Settings. To have jepso-ci build your repository immediately just click Test Hook. You can also rely on jepso-ci re-building your repository every time you push a commit.

To see live build status of your repository once the build has started just go to https://jepso-ci.com/paulmillr/es6-shim

You can see an example of what the badge would look like in your readme at jepso-ci-examples/es6-shim.

paulmillr added a commit that referenced this pull request Jan 26, 2013
@paulmillr paulmillr merged commit 3cde930 into paulmillr:master Jan 26, 2013
@ForbesLindesay
Copy link
Contributor Author

Thanks, this makes you the second project to use jepso-ci (that I don't have commit access to) 😄

@paulmillr
Copy link
Owner

Really neat stuff dude, had been waiting for something like this for a long. 👍 :octocat:

@ForbesLindesay
Copy link
Contributor Author

If you want to keep up to date on any jepso-ci developments you can follow it on twitter: https://twitter.com/jepsoci (expect a tweet about your repo having cross browser testing soon)

@paulmillr
Copy link
Owner

I can tweet about this thing of yours and you will be seen by ~700 devs excluding retweets. Just need to know if you’re planning to do some changes before launching to public unless it had been launched already.

@ForbesLindesay
Copy link
Contributor Author

That's fantastic (sadly I only have 23 followers so far, which doesn't get vast exposure). I'm considering it launched at the moment so tweet away. Any API changes I make will be backwards compatible with the current API.

There are obviously a number of things currently lacking, such as the fact that once lots of people are using it there will be a queue to get your repo built, and I don't currently give any indication of where in that queue each repo is. These are things I'm intending to iron out as the service becomes more popular though (at the moment it doesn't really cause any problems).

@Yaffle
Copy link
Contributor

Yaffle commented Jan 26, 2013

hm.... interesting service

@mathiasbynens
Copy link
Contributor

https://jepso-ci.com/ seems dead. Is this service still available, or should we remove these files from the repository?

@ljharb
Copy link
Collaborator

ljharb commented Dec 19, 2013

I agree - testling has suddenly become reliable again, and jepso seems barely maintained.

@paulmillr
Copy link
Owner

it was removed a846861

@mathiasbynens
Copy link
Contributor

Yeah but .jepso-ci.json is still there (fixed now: fe04f69) and so is the jepso-ci-specific code in test/browser-onload.js.

@ForbesLindesay
Copy link
Contributor Author

Sorry, I haven't really been maintaining jepso-ci lately. If I get time I will update it but it needs a lot of work to be a sensible maintainable service and unfortunately I have a day job.

@mathiasbynens
Copy link
Contributor

unfortunately I have a day job

Ah, the ultimate first world problem :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants