Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Update jenkins after sdk merge - Closes #3350 #3370

Merged
merged 11 commits into from
Apr 16, 2019

Conversation

fchavant
Copy link
Contributor

@fchavant fchavant commented Apr 16, 2019

What was the problem?

Jenkins configuration needed to be overhauled after the SDK merge.

How did I fix it?

Refactored Jenkinsfile according to requirements by @shuse2 and @ManuGowda

How to test it?

Look at

Review checklist

@fchavant fchavant self-assigned this Apr 16, 2019
@fchavant fchavant marked this pull request as ready for review April 16, 2019 13:24
@shuse2 shuse2 changed the title 3350 update jenkins after sdk merge Update jenkins after sdk merge - #3350 Apr 16, 2019
shuse2
shuse2 previously approved these changes Apr 16, 2019
Copy link
Contributor

@ManuGowda ManuGowda left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Jenkinsfile.sdk Outdated Show resolved Hide resolved
framework/Jenkinsfile Outdated Show resolved Hide resolved
@shuse2 shuse2 merged commit 702f960 into development Apr 16, 2019
@shuse2 shuse2 deleted the 3350-update_jenkins_after_sdk_merge branch April 16, 2019 14:22
@fchavant fchavant changed the title Update jenkins after sdk merge - #3350 Update jenkins after sdk merge - Closes #3350 Apr 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Jenkins for sdk need to be fixed according to the new structure
4 participants