Geni2 opened a new issue, #7097:
URL: https://github.com/apache/incubator-devlake/issues/7097

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When you collect data from Jenkins and you specify in the data scope only 
collect if that is a production deployment.
   But DevLake has no info if the stage `production deployment` on that job was 
running or it was skipped.
   
   The pipeline was successful but it's not a production deployment and it 
should not be marked as one.
   
![jenkins](https://github.com/apache/incubator-devlake/assets/51850738/378f92d7-c1a0-4587-a558-f39902ca591e)
   
   
   ### What do you expect to happen
   
   If the stage that I have specified in the data scope e.g. deploy production 
was skipped we should count that as a production deployment.
   
   ### How to reproduce
   
   1. Connect Jenkins with DevLake and make the configuration with the data 
scope.
   2. Make the configuration of the Scope Config.
   3. Create a Jenkins pipeline with 2 or 3 stages, the name is not important 
but call one stage `deploy prod`.
   4. Run the job and make sure the `deploy prod` was skipped but the pipeline 
was successful.
   5. If you go to the Grafana board you will see that the job was counted as a 
production deployment but in fact, that wasn't.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v0.19.0
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to