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

Feature/jenkins 38598 create pipeline from GitHub #794

Closed

Conversation

cliffmeyers
Copy link
Contributor

Description

Submitter checklist

  • Link to JIRA ticket in description, if appropriate.
  • Change is code complete and matches issue description
  • Appropriate unit or acceptance tests or explanation to why this change has no tests
  • Reviewer's manual test instructions provided in PR description. See Reviewer's first task below.
  • Ran Acceptance Test Harness against PR changes.

Reviewer checklist

  • Run the changes and verified the change matches the issue description
  • Reviewed the code
  • Verified that the appropriate tests have been written or valid explanation given

@reviewbybees

Cliff Meyers and others added 30 commits October 17, 2016 09:47
…il component is ready; integrate with existing router / background code so the existing screen's DOM will display under the dialog
…list and workflow steps in Create Pipeline
… XP; lay the groundwork for "re-entrant" flow; still needs to sandbox rendered content
…ender) so that we can have more flexibility with how we render untrusted React code
…the extension points in Create Pipeline flow
…ync w/ props.children and yielding incorrect statuses for steps; now we just track the current step index which is much simpler anyways
…eeds sharing between the two steps; enhance "CompletedStep" to display its progress via percent complete
…inate duplicate ContextBridge; update deps after beta publish
Eventually it should be moved out in it's own repo
Cliff Meyers added 9 commits January 31, 2017 14:14
…s for org folder detection and configuration
…, error state, added button to navigate back to Dashboard
…-github

# Conflicts:
#	blueocean-core-js/npm-shrinkwrap.json
#	blueocean-core-js/package.json
#	blueocean-dashboard/npm-shrinkwrap.json
#	blueocean-dashboard/package.json
#	blueocean-personalization/npm-shrinkwrap.json
#	blueocean-personalization/package.json
#	blueocean-web/npm-shrinkwrap.json
#	blueocean-web/package.json
@i386
Copy link
Contributor

i386 commented Feb 7, 2017

I am going to start testing

Cliff Meyers added 2 commits February 7, 2017 10:05
…-github

# Conflicts:
#	blueocean-dashboard/npm-shrinkwrap.json
#	blueocean-dashboard/package.json
#	blueocean-personalization/npm-shrinkwrap.json
#	blueocean-personalization/package.json
#	blueocean-web/npm-shrinkwrap.json
#	blueocean-web/package.json
@michaelneale
Copy link
Member

Looking good - put feedback in the doc

Cliff Meyers added 11 commits February 8, 2017 10:29
…k unless show() was called first - even though the indicator is still visible by default
…-github

# Conflicts:
#	blueocean-dashboard/npm-shrinkwrap.json
#	blueocean-dashboard/package.json
#	blueocean-personalization/npm-shrinkwrap.json
#	blueocean-personalization/package.json
#	blueocean-web/npm-shrinkwrap.json
#	blueocean-web/package.json
@michaelneale
Copy link
Member

Tried latest "mocked" version - LGTM.

One small :nit: was that when it was busy creating, it didn't disable the git/github buttons right at the top is all but I think can proceed.

…-github

# Conflicts:
#	blueocean-dashboard/npm-shrinkwrap.json
#	blueocean-dashboard/package.json
#	blueocean-personalization/npm-shrinkwrap.json
#	blueocean-personalization/package.json
#	blueocean-web/npm-shrinkwrap.json
#	blueocean-web/package.json
@cliffmeyers
Copy link
Contributor Author

Closing in favor of #812

@cliffmeyers cliffmeyers deleted the feature/JENKINS-38598-create-pipeline-from-github branch May 22, 2017 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants