Countdown to 1.4

[jaredly]

The few remaining things

• [x] strider-sauce
  • [x] config page
  • [ ] everything else
• [x] strider-heroku
  • [x] oauth
  • [x] config page
  • [x] deployment
• [x] build page: load job data for a running job
• [ ] strider-hg would be super easy
• [x] "manual add" a repository
• [x] strider-webhooks
• [ ] build badges

Here are the things as I see it that need to be completed & tested before we release 1.4

Strider Webapp

• [x] dashboard
  • [x] basic display of jobs, public & private
  • [x] start test / deploy job
  • [x] react to "browser.update" events from the server
  • [x] react to "job.new" events from the server
  • [x] testing!
• [x] config page
  • [x] basic population of data
  • [x] branch switching
  • [x] plugin ordering / enabling
  • [x] save basic configuration
  • [x] reload branch list (ui button)
  • [x] kickoff build button from the config page. Takes you to the build page.
  • [x] generate new ssh keypair
  • [ ] [low] show plugin documentation on mouseover

• [x] build page
  • [x] initial population of data
  • [x] kickoff test / deploy run
  • [x] react to "browser.update" events from the server
  • [x] react to "job.new" events from the server
  • [x] job history navigation
  • [ ] [low] job history paging? We currently only show the latest 20

• [x] projects page
  • [x] list unconfigured providers
  • [x] list repos for each configured provider, grouped according to organization
  • [x] add / remove button per repo.
  • [x] use provider's setup/teardownRepo when adding/removing project
  • [x] refresh list

• [x] user account page
  • [x] provider config
  • [x] add account
  • [x] delete account
• [ ] admin/runners page (low)
  • [ ] global configuration for runners
  • [ ] list all jobs
• UI Integration tests
  • [x] fixtures with ?test
  • [x] dashboard
  • [x] build page
  • [x] config
  • [x] projects
  • [x] selenium tests
  • [x] dashboard
  • [x] build page
  • [x] config
  • [x] projects

    Running jobs

• [x] strider-extension-loader
• [x] strider-simple-runner
• [ ] documentation updates everywhere for the final API
• [ ] tests

  New Plugins

• [x] strider-git
  • [x] getFile
  • [x] getBranches
  • [x] config page
  • [x] fetch
• [x] strider-github
  • [x] webhooks (commit + pull requests)
  • [x] create account
  • [x] setupRepo
  • [x] teardownRepo
  • [x] getFile
  • [x] getBranches
  • [x] listRepos
  • [x] fetch
• [ ] strider-bitbucket
  • [x] webhooks
  • [x] create account
  • [x] setupRepo
  • [x] teardownRepo
  • [x] getFile
  • [x] getBranches
  • [x] listRepos
  • [x] fetch
  • [ ] mercurial support

    Update Core Plugins to new API + config

• [x] strider-env
• [x] strider-custom
• [x] strider-python
• [x] strider-node
• [ ] strider-go
• [x] strider-sauce
• [ ] strider-qunit
• [ ] strider-jelly

  Nice to have

• [ ] strider-docker
• [ ] some other provider. maybe gitlab? their api looks pretty straightforward

[niallo]

Thanks. Added this issue to the 1.4 milestone. Lots for us to crank through over the next couple of weeks !!

[jaredly]

See updates

[marekventur]

Is there a rough ETA yet? I'd really like to update, but HEAD seems to be a bit unstable at the moment ;)

[jaredly]

We're working on testing & bugfixes right now -- I'm thinking we'll be ready to call it beta by the end of this week.

[marekventur]

Thanks! I appreciate all the work you put into it - keep it up!

[marekventur]

Sorry for the annoying question, but does the closing of this ticket mean 1.4 is ready yet? Is there a blog or similar where I can keep track of the progress?

[jaredly]

This means that everything that was on the list (that will be in 1.4) is done. check out the 1.4 milestone in the issues list to see how close we are

[marekventur]

Thanks!