Thanks Martin, though you just reworded my post.

But yes one approach to consider is being able to store which, for example, 
versions have been run by deploy-to-sandox. IOW if deploy-to-sandbox has 
run with versions 1.0.0 and 1.0.4, I want to store those versions in its 
property file, say sandboxed_versons.properties. How will I then tell 
deploy-to-staging to read /.../deploy-to-sandbox/sandboxed.properties file?

Chris

On Saturday, November 10, 2018 at 9:35:12 PM UTC-5, Martin d'Anjou wrote:
>
> I do not know of an automated way of doing that.
>
> If I understand correctly, the release number is assigned by the 
> build-and-test phase, and it published the docker repo.
> I assume that this release number is known one way or another by the 
> users, since it has been published to the docker repo.
> This release number is an input to the other jobs. So I suggest you make 
> the release number an input parameter to the other jobs.
>
> When each job runs, it needs to check that the released artifact has 
> reached the expected "quality" level for the job. If not the jobs would 
> fail with some meaningful error message.
> The quality levels would be 1) built and tested, 2) sandbox, 3) staging, 
> and 4) production.
> In other words, deploy-to-sandbox(1.0.11) needs to check that the 
> artifacts 1.0.11 exists in the docker repo before it attempts to deploy to 
> sandbox.
> You also need to store the quality level somewhere persistent, maybe as a 
> property of the artifacts in the docker repo (if that is possible?).
> Artifactory supports properties, or maybe you need a database.
>
> Hope this helps at least from a conceptual point of view.
>
> Martin
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/74f83fca-f847-49d7-bbc5-a157feaa10cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to