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

Fix our continuous release process #271

Merged
merged 5 commits into from
Jan 8, 2018
Merged

Conversation

jlewi
Copy link
Contributor

@jlewi jlewi commented Jan 7, 2018

  • Fix our continuous release process which is broken (Fix the releaser so we can build new images #270)

  • Docker image used to build releases needs YARN and NodeJs to build the FE.

  • We refactored release.py and split cloning and building the code into two steps in Make cloning the repo and building the artifacts separate commands in py/release.py #189. So we had to refactor how we build from the latest green to account for these changes.

    • release.py no longer has a function to periodically check the latest post submit and rebuild if necessary
    • Created a simple shell script launch_build.sh to check out the latest green commit and then build
      the code; We invoke the build function in the code checked out.
  • Our releaser has been crash looping and not released any new images since 12/23.


This change is Reviewable

@coveralls
Copy link

coveralls commented Jan 7, 2018

Coverage Status

Coverage remained the same at 28.374% when pulling 4705d32 on jlewi:fix_releaser into 190394d on tensorflow:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 28.374% when pulling 10f3511 on jlewi:fix_releaser into 190394d on tensorflow:master.

@@ -45,7 +52,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \

RUN easy_install pip
RUN pip install --upgrade six pyyaml google-api-python-client \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggest using Pipfile to lock down python dependencies

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a TODO. I tried to make it work but ran into problems. I'd rather get this PR submitted because it fixes our releases which is needed to get a Docker image out that works for the FE.
So I don't think its worth delaying to try to make pipenv work.

jlewi added 2 commits January 7, 2018 19:50
* We'd split release into two steps cloneing and building the code so
  we have to update the code.
@jlewi jlewi changed the title Add YARN and NodeJs to our releaser image. Fix our continuous release process Jan 8, 2018
@coveralls
Copy link

coveralls commented Jan 8, 2018

Coverage Status

Coverage remained the same at 28.374% when pulling d73ce50 on jlewi:fix_releaser into 190394d on tensorflow:master.

@jlewi
Copy link
Contributor Author

jlewi commented Jan 8, 2018

Thanks @jimexist PTAL.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 28.374% when pulling d73ce50 on jlewi:fix_releaser into 190394d on tensorflow:master.

@coveralls
Copy link

coveralls commented Jan 8, 2018

Coverage Status

Coverage remained the same at 28.374% when pulling 86f4216 on jlewi:fix_releaser into 190394d on tensorflow:master.

@jlewi
Copy link
Contributor Author

jlewi commented Jan 8, 2018

@jimexist any additional comments?

Copy link
Member

@jimexist jimexist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jlewi
Copy link
Contributor Author

jlewi commented Jan 8, 2018

Thanks.

@jlewi jlewi merged commit 9c93d5f into kubeflow:master Jan 8, 2018
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.

3 participants