You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a DevOps Engineer we would like to demonstrate a global-workflow CI test framework with the same capabilities as our current BASH/GitHub CLI solution using a Jenkins Server/Agent System on Orion and Hera.
What are the requirements for the new functionality?
We should be able to interact with the Jenkins system using GItHub similarly as the BASH system does so as not to disrupt the user experience with the CI global-workflow capability. In the long run we will have BASH on WCOSS2 and Jenkins on RDHPCS but the front-end experience for the user will be identical.
Acceptance Criteria
We can demonstrate a working Jenkins Pipeline script that can build and run a CI tests and have its status reflected with GitHub Labels,
Suggest a solution (optional)
Move away from launching with labels and use Dispatch Actions to start Jenkins.
Set up a working example to show this capability described above so can be used with EPICS Server/Agent instance running in AWS.
The text was updated successfully, but these errors were encountered:
What new functionality do you need?
As a DevOps Engineer we would like to demonstrate a global-workflow CI test framework with the same capabilities as our current BASH/GitHub CLI solution using a Jenkins Server/Agent System on Orion and Hera.
What are the requirements for the new functionality?
We should be able to interact with the Jenkins system using GItHub similarly as the BASH system does so as not to disrupt the user experience with the CI global-workflow capability. In the long run we will have BASH on WCOSS2 and Jenkins on RDHPCS but the front-end experience for the user will be identical.
Acceptance Criteria
We can demonstrate a working Jenkins Pipeline script that can build and run a CI tests and have its status reflected with GitHub Labels,
Suggest a solution (optional)
Move away from launching with labels and use Dispatch Actions to start Jenkins.
Set up a working example to show this capability described above so can be used with EPICS Server/Agent instance running in AWS.
The text was updated successfully, but these errors were encountered: