Hi,
This is my first time trying anything regarding building plugins, so
perhaps I'm doing something wrong.
I) I installed maven 3 onto a linux machine
2) created a settings.xml file for it with the contents shown in the
"Setting up Environment" section of this page
https://wiki.jenkins-ci.or
is not by standard conventions a nested class within the Publisher itself
> but in a separate class in the same package. Perhaps that is messing up
> the Publisher to Descriptor lookup.
>
> /B
>
> On Thu, Jul 7, 2016 at 12:37 PM, Jonathan Hodgson > wrote:
>
>> Hi,
>
d uploading the plugin,
it's now working.
And it seems to do what I need, which is great news.
On Thursday, July 7, 2016 at 2:42:14 PM UTC+1, Jonathan Hodgson wrote:
>
> Ok, that's interesting, but perhaps you could clarify? As I said this is
> my first foray into plugin developm
Hi,
this has me mystefied.
I am trying to write groovy code for a pipeline build which extracts some
information from a config file, and in the process have run into what seems
like a bug, but perhaps I'm just not understanding something.
As a stand alone test to check my code I produced the f
Thanks,
Are these sorts of issues documented anywhere? I lost a day on this, and
thought I must be losing my sanity at one point because if you don't
understand the inner working of groovy (and I currently don't) then it's a
very mysterious looking problem.
--
You received this message becaus
I don't seem to have an option to add issues on Jira, so I'll have to
report this here
I have a pipeline job that takes various parameters (all supplied by a
script on a remote machine invoking the build).
The problem is, that if those parameters get too large, shell scripts
called from jenkin
cker.
>
> https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue
>
> Include a complete Jenkinsfile/job configuration/whatever else is needed
> to reproduce this issue from scratch.
>
> > On 28.09.2016, at 16:41, Jonathan Hodgson > wrote:
> >
>
On Wednesday, September 28, 2016 at 4:12:21 PM UTC+1, Jesse Glick wrote:
>
> On Wed, Sep 28, 2016 at 10:41 AM, Jonathan Hodgson
> > wrote:
> > this seems to be recent
>
> As of Pipeline: Job 2.7, build parameters will be in your environment,
> not just as Groov
On Wednesday, September 28, 2016 at 4:26:39 PM UTC+1, slide wrote:
>
> Is there a reason you can't send the path to the file that the diff comes
> from?
>
>>
>>
Because the diff is created on a remote machine, the one requesting the
build. so it has to be a push operation.
What I'm basically
Well I can now see a "Create" button on the JIRA homepage.
I don't know if that changed while I was out, or if it's just a result the
break/walk in the fresh air/coffee returning some sanity to my mangled
brain, but I will put together a proper bug report on there now.
--
You received this mes
Ticket now created
https://issues.jenkins-ci.org/browse/JENKINS-38576
I further streamlined my scripts to isolate the issue. Basically as soon as
any single parameter goes over a certain length (13065 characters in my
tests) all shell scripts stop working
--
You received this message because
Hi,
I'm wondering what the rules/etiquette are on this.
If a bug is actually preventing me from progressing in my work, can I
elevate its priority to blocker?
If not, then is there another way I can give it a bump so I know someone's
had another look? I understand not everything can be fixed a
Hi,
Last I checked File Parameters did not work in pipeline jobs (despite being
offered as an option in the UI)
It is mentioned here, but I see no indication of any work happening on it
https://issues.jenkins-ci.org/browse/JENKINS-27413
I've gone through hell trying to work around this issue
On Monday, October 10, 2016 at 5:43:51 PM UTC+1, Jesse Glick wrote:
>
> On Mon, Oct 10, 2016 at 12:28 PM, Jonathan Hodgson
> > wrote:
> > is there any prognosis on when this stuff might actually work?
>
> Not currently being worked on AFAIK. One priority among man
Hi,
Groovy in Jenkins has some quirks and they're really driving me nuts.
Some of the very neat features of Groovy, such as closures and .each() and
.findAll() don't work as advertised. Which is a problem because it's these
neat ways of doing things that are always used when you google a proble
On Thursday, October 13, 2016 at 6:59:16 PM UTC+1, Baptiste Mathus wrote:
>
> Hi, please use the users list if this is to discuss Pipeline usage.
>
I'm sorry, since the big selling point of Jenkins 2 was that pipelines are
now integral to the Jenkins plan, and since this is not user error I'm
>
>
>
> > But the problem I described as a case in point doesn't seem to fall
> under that umbrella.
>
> Explanation here:
> https://github.com/jenkinsci/workflow-cps-plugin/#technical-design
>
>
>
Thanks. that helps explain things.
Though my confusion is increased by the fact that right now
Hi,
Although I'm an experienced programmer, I'm still learning about Jenkins as
a user and also as to what goes on under the hood.
My builds are at their early stages, and I can already see that artifacts
are going to become unwieldy.
So i"m wondering whether it would be possible, and what wou
18 matches
Mail list logo
