When I tried to download the build pipeline plugin, the download is
failing before finishing..the 2.4 mb . Please help
--
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
Greetings,
I'm working thru the book 'Jenkins, The Definitive Guide'
Jenkins 2.0, Java 8 update 92, Maven 3.3.9 on Windows.
Jenkins is installed, game of life built fine.
This problem relates to the section "More Reporting - Displaying Javadocs".
The maven target javadoc:javadoc fails with
Hi
How can I restrict who can actually approve a manual (i.e. input) step in a
pipeline? If I have a "Deploy to PROD" step I only want people with a
particular role to be able to approve. Am I going about it the wrong way?
Thanks
Lionel.
--
You received this message because you are
Norm,
Take a look at this my posting from a few months ago:
https://groups.google.com/d/msg/jenkinsci-users/P7VMQQuMdsY/bHfBDSn9GgAJ
That link has pointers to the Groovy Script class and Groovy shell.
I think understanding those two classes will help improve your understanding
of Pipeline
Unless you're talking about your method declaration *def mapToList()*. In
that case, the def is just window dressing AFAIK. The return type is the
same with or without *def*: ie, *Object*.
On Wednesday, April 27, 2016 at 3:34:24 PM UTC-7, Brian Ray wrote:
>
> Nice hackaround. I will try that in
Did make use of the "Replay" feature at all to troubleshoot your script,
Norbert? Just curious.
https://jenkins.io/blog/2016/04/14/replay-with-pipeline/
On Wed, Apr 27, 2016 at 3:34 PM, Brian Ray wrote:
> Nice hackaround. I will try that in the uncooperative parts of my
Hi Brian,
every single method in the "final foo" - including the String
Constructor requires approval. I was hoping for a proper subset that would
work within the sandbox.
What I ended with (several dozen "Builds" later ) is using a helper
function squeezing the map into a list, seems the
Prior to the pipeline/Jenkinsfile modus operandi, I would have done the
following:
1. Created Jenkins "Maven project" jobs for each separate project, with
triggers/hooks set to build them when changes are found.
2. Used the builtin triggers to "Build whenever a dependency changes" to
handle
I would guess that one or more of your jobs may have had their "Repository
browser" switched from one value to the first value in the list,
AssemblaWeb. I don't know why that would happen, but I've seen it happen
at least a few times in my interactions with Jenkins and the git plugin.
Configure
I am running Jenkins v.1642.3. I just saw the following in the Jenkins log. Any
idea was causes this and how it can be resolved?
Apr 27, 2016 12:51:47 PM WARNING
hudson.model.Descriptor$NewInstanceBindInterceptor instantiate
falling back to default instantiation
Side note: The map keys and values are simply *String*s.
On Wednesday, April 27, 2016 at 9:26:51 AM UTC-7, Brian Ray wrote:
>
> FWIW I recently replaced several C-style loops with *for ( x in y )* for
> iterating over both lists and maps in CPS code and for the most part
> conversion went fine.
Hi,
I'm using Jenkins 1.625.2 on Windows and I was wondering if there was a way
to trigger a build only on certain file types. Right now my build runs on
every checkin and I'd like to narrow it to down to a few type of checkins.
thanks,
--
You received this message because you are
On Tuesday, April 26, 2016 at 7:18:55 PM UTC-4, Norbert Lange wrote:
>
> There seem to be some arcane rules on how to iterate over some
> builtin Groovy/Java Types within a sandbox. I haven`t found a way that
> works without manually allowing the function.
Which methods did you need to
There is now a replaceAction() where you can just pass a new action
(Parameter) with the same name and it will replace it :)
http://javadoc.jenkins-ci.org/hudson/model/Actionable.html#replaceAction%28hudson.model.Action%29
On Friday, August 3, 2012 at 5:52:17 PM UTC+2, Reuben Gow wrote:
>
>
>> It's a known issue. We just haven't had the time to restore this service
>> between everything else going on right now.
No worries Daniel, I appreciate that things are busy at the moment.
Matthew
--
This e-mail and any attachments may contain confidential, copyright and or
privileged
> On 27.04.2016, at 11:20, matthew.web...@diamond.ac.uk wrote:
>
> If I go to the Jenkins Changelog page (new wiki version) at
> https://jenkins.io/changelog/, and click "Community ratings", I do _not_ see
> the individual ratings for each release. I tried using a number of different
>
In addition to mention:
The "Snippet Generator" provides documentation on this:
*Password Parameter*s, or any other type of build parameters selected for
masking in Hudson's/Jenkins' main configuration screen (*Manage Hudson* >
*Configure
System*), will be automatically masked.
And also
I created a masked password FOO with "1234".
Here my simple test DSL script:
node {
stage "ONE"
wrap([$class: 'MaskPasswordsBuildWrapper']) {
echo "FOO=${FOO}"
}
}
Independent whether I check "Prepare an environment for the run" or not ...
I get this:
Wow, this is strange!
To be honest, my test case was a freestyle job and I assumed there should
be no difference.
I tried again and it really works in pipeline, but not in freestyle job -
with exact same credential binding and same shell script!
So I think this can help to fix JENKINS-24805
So
If I go to the Jenkins Changelog page (new wiki version) at
https://jenkins.io/changelog/, and click "Community ratings", I do _not_ see
the individual ratings for each release. I tried using a number of different
browsers on different OSes.
Does anyone else have this problem?
Thanks
Matthew
20 matches
Mail list logo