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

Find ready branches (nextup) #63

Open
lakruzz opened this issue Feb 20, 2017 · 7 comments
Open

Find ready branches (nextup) #63

lakruzz opened this issue Feb 20, 2017 · 7 comments

Comments

@lakruzz
Copy link
Owner

lakruzz commented Feb 20, 2017

git co `git phlow nextup --prefix $BRANCH` #implies "git fetch remote()"
git phlow deliver --local --test $TESTSCRIPT 
@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

Imagine the we're on the concourse worker or jenkins slave.

We are "the pip job"

there are two ready branches
image

...and, they are both waiting to be merged:

image

@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

The new nextupcommand takes a --list switch, which is most useful to humans - as it shows a list ... Without the switch it simply returns the next:

image

@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

This makes it useful in the context of a checkout:

image

@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

At this point it's essentially a local deliver - and deliver is now purging, so the result becomes:

image

@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

Next is served simply by running again:

image

And after that, there aren't any more

image

@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

One step further - now we just need to implement the the --test switch to #67 to have our two command PiP emulator

@lakruzz
Copy link
Owner Author

lakruzz commented Feb 22, 2017

@groenborg

@lakruzz lakruzz reopened this Nov 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant