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

Countdown to 1.4 #197

Closed
78 of 95 tasks
jaredly opened this issue Sep 26, 2013 · 8 comments
Closed
78 of 95 tasks

Countdown to 1.4 #197

jaredly opened this issue Sep 26, 2013 · 8 comments
Milestone

Comments

@jaredly
Copy link
Member

jaredly commented Sep 26, 2013

The few remaining things

  • strider-sauce
    • config page
    • everything else
  • strider-heroku
    • oauth
    • config page
    • deployment
  • build page: load job data for a running job
  • strider-hg would be super easy
  • "manual add" a repository
  • 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

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

screen shot 2013-10-06 at 3 43 50 am

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

screen shot 2013-10-06 at 3 43 27 am

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

screen shot 2013-10-06 at 3 41 55 am

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

Running jobs

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

New Plugins

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

Update Core Plugins to new API + config

  • strider-env
  • strider-custom
  • strider-python
  • strider-node
  • strider-go
  • strider-sauce
  • strider-qunit
  • strider-jelly

Nice to have

  • strider-docker
  • some other provider. maybe gitlab? their api looks pretty straightforward
@niallo
Copy link
Member

niallo commented Sep 26, 2013

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

@jaredly
Copy link
Member Author

jaredly commented Oct 6, 2013

See updates

@marekventur
Copy link
Contributor

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

@jaredly
Copy link
Member Author

jaredly commented Oct 21, 2013

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
Copy link
Contributor

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

@jaredly jaredly closed this as completed Nov 9, 2013
@marekventur
Copy link
Contributor

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
Copy link
Member Author

jaredly commented Nov 11, 2013

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
Copy link
Contributor

Thanks!

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

No branches or pull requests

3 participants