streampipes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <>
Subject Re: CI Pipelines
Date Thu, 12 Dec 2019 13:03:15 GMT
Hi all,

it is possible to specify secret credentials in Jenkins and assign a name to them.
We are using this feature in the PLC4X sonar-cloud tests.
Here I deployed my sonarcloud login token to Jenkins and gave it a name.
I then use this name to get the credentials and use them in the build.

Perhaps this would allow the other option? But haven't checked this option.


´╗┐Am 12.12.19, 12:02 schrieb "Dominik Riemer" <>:

    Hi Justin,
    thanks for clarifying!
    One question, in the Docker section of the draft guidelines, snapshots are
    currently explicitly mentioned:
    * Release candidates, nightlys or snapshots need to be clearly tagged.
    * The latest tag should not point to an artifact containing unapproved code
    e.g. to master or dev branches or to a RC or snapshot.
    We would plan to do exactly like that, having releases using both the
    "latest" tag and a version tag and clearly tag snapshots/nightlys with a
    SNAPSHOT appendix. The SNAPSHOT images would not be advertised in any way
    and only be mentioned in core developer guides. 
    Would this be ok from a policy point of view?
    -----Original Message-----
    From: Justin Mclean <> 
    Sent: Thursday, December 12, 2019 12:43 AM
    Subject: Re: CI Pipelines
    >  I'd personally prefer to use the 2nd way proposed in the Docker Hub 
    > release policy 
    > elines
    There are draft guidelines and really only deal with voted on released
    artefacts, and as such not really suitable for a CI pipeline. Note they case
    you need to point to a released tag not master or develop branches.

View raw message