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

Version problem in Jenkins REEF #1084

Open
JunhoeKim opened this issue Mar 30, 2017 · 3 comments
Open

Version problem in Jenkins REEF #1084

JunhoeKim opened this issue Mar 30, 2017 · 3 comments
Labels

Comments

@JunhoeKim
Copy link
Contributor

JunhoeKim commented Mar 30, 2017

In latest version of REEF, a new configuration in client ON_JOB_SUBMITTED is updated. So when we try to customize DriverLauncher code in REEF. Jenkins fails to build.

@JunhoeKim JunhoeKim added bug and removed bug labels Mar 30, 2017
@yunseong yunseong added bug test and removed bug labels Mar 30, 2017
@yunseong
Copy link
Contributor

The main reason for this failure is our code depends on the REEF's latest SNAPSHOT. Whenever we need new features in REEF, we have to manually build REEF and include it to Jenkin's local repository.

It'd be great if we find an elegant way for Jenkins to use the latest version of REEF automatically.

@wynot12
Copy link
Contributor

wynot12 commented Mar 30, 2017

It looks that it has been resolved by @yunseong as we can see that Jenkins has successfully tested #1081.
Shall we close it?

@yunseong
Copy link
Contributor

yunseong commented Mar 30, 2017

IMHO, we'd better find a way to rebuild REEF automatically somehow.

I think we can add another project to Jenkins, which tests & builds Cay periodically (e.g., daily), and there we can set the pre-built step to building the latest version of REEF (after git pull) in the project.

This way we can 1) prevent the regular build taking long to build REEF, and 2) display the build status.

Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants