-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
We have a pipeline setup which allows us to build and deploy in two modes:
- build everything from scratch and deploy
- look at the previous deployment and build and deploy only incrementally
We do (1) at the inception of a project, then normally we do (2) because it's very fast - we build and deploy a lot on a daily basis.
However sometimes we need to do type 1 of deployments when there is a disruption.
The interleaving of types 1 and 2 of deployments disrupts the progress bar's accuracy for each stage for both types.
We could calculate how long a stage is expected to take based on historical data and type 1 vs 2 of deployments, however there is no way to set a stage to have an expected duration.
The alternative would be to create separate jobs for type 1 and type 2 of deployments. This approach puts lots of pressure on the infrastructure code. We already use a multibranch pipeline and we feel like duplicating our pipeline for each type 1 vs 2 would increase the maintanance cost.
Thus we'd like to be able to tell jenkins what the expected duration for a pipeline step would be, as an opt-in feature. Not setting it would keep things as they are now.
Regards,
Flavius Aspra
[JENKINS-44792] Ability to set expected duration for a pipeline stage
Flavius Aspra
created issue -
Flavius Aspra
made changes -
| Description |
Original:
We have a set pipeline setup which allows us to build and deploy in two modes: # build everything from scratch and deploy # look at the previous deployment and build and deploy only incrementally We do (1) at the inception of a project, then normally we do (2) because it's very fast - we build and deploy a lot on a daily basis. However sometimes we need to do type 1 of deployments when there is a disruption. The interleaving of types 1 and 2 of deployments disrupt the progress bar's accuracy for each stage for both types. We could calculate how long a stage is expected to take based on historical data and type 1 vs 2 of deployments, however there is no way to set a stage to have an expected duration. The alternative would be to create separate jobs for type 1 and type 2 of deployments. This approach puts lots of pressure on the infrastructure code. We already use a multibranch pipeline and we feel like duplicating our pipeline for each type 1 vs 2 would increase the maintanance cost. Thus we'd like to be able to tell jenkins what the expected duration for a pipeline step would be, as an opt-in feature. Not setting it would keep things as they are now. Regards, Flavius Aspra |
New:
We have a pipeline setup which allows us to build and deploy in two modes: # build everything from scratch and deploy # look at the previous deployment and build and deploy only incrementally We do (1) at the inception of a project, then normally we do (2) because it's very fast - we build and deploy a lot on a daily basis. However sometimes we need to do type 1 of deployments when there is a disruption. The interleaving of types 1 and 2 of deployments disrupt the progress bar's accuracy for each stage for both types. We could calculate how long a stage is expected to take based on historical data and type 1 vs 2 of deployments, however there is no way to set a stage to have an expected duration. The alternative would be to create separate jobs for type 1 and type 2 of deployments. This approach puts lots of pressure on the infrastructure code. We already use a multibranch pipeline and we feel like duplicating our pipeline for each type 1 vs 2 would increase the maintanance cost. Thus we'd like to be able to tell jenkins what the expected duration for a pipeline step would be, as an opt-in feature. Not setting it would keep things as they are now. Regards, Flavius Aspra |
Flavius Aspra
made changes -
| Description |
Original:
We have a pipeline setup which allows us to build and deploy in two modes: # build everything from scratch and deploy # look at the previous deployment and build and deploy only incrementally We do (1) at the inception of a project, then normally we do (2) because it's very fast - we build and deploy a lot on a daily basis. However sometimes we need to do type 1 of deployments when there is a disruption. The interleaving of types 1 and 2 of deployments disrupt the progress bar's accuracy for each stage for both types. We could calculate how long a stage is expected to take based on historical data and type 1 vs 2 of deployments, however there is no way to set a stage to have an expected duration. The alternative would be to create separate jobs for type 1 and type 2 of deployments. This approach puts lots of pressure on the infrastructure code. We already use a multibranch pipeline and we feel like duplicating our pipeline for each type 1 vs 2 would increase the maintanance cost. Thus we'd like to be able to tell jenkins what the expected duration for a pipeline step would be, as an opt-in feature. Not setting it would keep things as they are now. Regards, Flavius Aspra |
New:
We have a pipeline setup which allows us to build and deploy in two modes: # build everything from scratch and deploy # look at the previous deployment and build and deploy only incrementally We do (1) at the inception of a project, then normally we do (2) because it's very fast - we build and deploy a lot on a daily basis. However sometimes we need to do type 1 of deployments when there is a disruption. The interleaving of types 1 and 2 of deployments disrupts the progress bar's accuracy for each stage for both types. We could calculate how long a stage is expected to take based on historical data and type 1 vs 2 of deployments, however there is no way to set a stage to have an expected duration. The alternative would be to create separate jobs for type 1 and type 2 of deployments. This approach puts lots of pressure on the infrastructure code. We already use a multibranch pipeline and we feel like duplicating our pipeline for each type 1 vs 2 would increase the maintanance cost. Thus we'd like to be able to tell jenkins what the expected duration for a pipeline step would be, as an opt-in feature. Not setting it would keep things as they are now. Regards, Flavius Aspra |
| Component/s | New: pipeline-stage-view-plugin [ 21139 ] | |
| Component/s | Original: pipeline [ 21692 ] |