I found this groovy script to create a global environment variable in
Jenkins.
Env.groovy:
import hudson.EnvVars;
import hudson.slaves.EnvironmentVariablesNodeProperty;
import hudson.slaves.NodeProperty;
import hudson.slaves.NodePropertyDescriptor;
import hudson.util.DescribableList;
import
Hello All!
I was trying to create a new Declarative pipeline script Step for
'SelfPromotion' and am confused as to what goes inside the start() method
while creating the step.
public StepExecution start() throws Exception{
return new Execution();
}
Here I later implement "Execution
Looks like the is missing git@ in the github url.
On Tue, Jun 11, 2019 at 1:36 PM Jesse Glick wrote:
> On Tue, Jun 11, 2019 at 4:21 PM Slide wrote:
> > Seems like its picking up the scm info from here
> https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L39, but I am
> not sure why
On Tue, Jun 11, 2019 at 4:21 PM Slide wrote:
> Seems like its picking up the scm info from here
> https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L39, but I am not
> sure why it would do that.
Presumably because it was not overridden properly.
I would encourage everyone,
Seems like its picking up the scm info from here
https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L39, but I am
not sure why it would do that. Can you run `mvn help:effective-pom` to see
if something weird is going on?
On Tue, Jun 11, 2019 at 12:54 PM Thomas POUIT wrote:
> Hello,
>
Hello,
I'm trying to publish my new plugin, but I get a
"jenkinsci/plugin-pom.git/
is not a valid repository name" error. I do not understand why it is trying
to publish under plugin-pom.git. Nowhere in my sources I refer to a
plugin-pom repo!
Here is the exact error message:
[INFO]
Is it possible to add a new column (via plugin) in the table in Build
History page?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Yes that shoud work. Although I think for a user it would be easier to have
a cli command or api method to populate the env variable in Jenkins. Since
in systems which are not isolated, storing a credentials in plain text can
involve risk.
Here is a small example from Travis,
Travis has CLI
What I do for this is set the SECRETS environment variably and point it to
a directory on the file system which had the secrets in it.
Basically pretending I’m using docker secrets
Thanks
Tim
On Tue, 11 Jun 2019 at 10:27, Parichay Barpanda
wrote:
> Thanks Gaven. Groovy is cool but we are using
Thanks Gaven. Groovy is cool but we are using JCasC yaml to create
credentials. I want to populate an environment variable and use it in my
config.yaml. I want to know if there is a way to do it without using docker
secrets. For example, when running Jenkins instance inside a VM or using
10 matches
Mail list logo
