Re: Wiki plugin page change

[fkpkot]

Thanks for the quick reply.


On Wednesday, December 27, 2017 at 11:33:26 AM UTC+2, Daniel Beck wrote:
>
>
> > On 27. Dec 2017, at 08:14, fkp...@gmail.com  wrote: 
> > 
> > I've noticed the plugin wiki page have changed to directly point to the 
> new wiki page but the new page also holds links to the previous page 
> forming some kind of circular confusing linking. 
>
> We currently have nobody who works on the plugin site, so the link to 
> plugins.jenkins.io in place of the old plugin info block remains for now 
> even on plugins.jenkins.io. 
>
> PRs welcome at https://github.com/jenkins-infra/plugin-site-api 
>
> > Moreover, the new page doesn't link clearly to the Jira issue system. 
>
> This is tracked as https://issues.jenkins-ci.org/browse/WEBSITE-334 
>
> > Are there any new wiki page guidelines for plugin maintainers? 
>
> You can continue editing the wiki page, those changes will show up on the 
> plugin site, where the statistics and metadata now live. 
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3a1969e7-51c4-4208-b59a-843d3d79cc95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wiki plugin page change

[fkpkot]

Hi,
I'm the maintainer of 
https://plugins.jenkins.io/hp-application-automation-tools-plugin .

I've noticed the plugin wiki page have changed to directly point to the new 
wiki page but the new page also holds links to the previous page forming 
some kind of circular confusing linking.
Moreover, the new page doesn't link clearly to the Jira issue system.

Are there any new wiki page guidelines for plugin maintainers?

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/21c80d32-bb20-4db7-9d03-a8c677f91eb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Custom update center won't replace the original plugin version in Jenkins update center

[fkpkot]

Hi,
I've used the following guide: 
https://github.com/ikedam/backend-update-center2/wiki/How-to-create-your-own-Jenkins-Update-Center

 to deliver beta versions to our customers 
(https://hpsa.github.io/JenkinsPluginUpdateCenter/update-center.json).

After several issues  - I've made it work but now, the Jenkins update won't 
display the plugin bet version unless i specifically delete the official 
Jenkins update center for few minutes and make Jenkins check the plugins 
again.

Anybody has a clue or any smarter solution?

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/bb04be61-cbcb-4268-97ce-7ad8c85c3e07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dual distribution managment

[fkpkot]

Hi,
I'd like to release to two different repositories - Jenkins and another 
local Repository (For specific testing purposes which requires an internal 
artificat).
In order to support such setup, I'd like to make our distribution 
management in POM file with variables set by maven properties (to be later 
overriden with maven Settings file).

As far as i know - such setup should make any issues but just to remove any 
possibility of Murphy's law strike :) 

Is there any known issue with such setup?
Any possible issues that might occur due to such setup?

Thanks ahead.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7c2d21fc-6433-4b54-8e7a-2a01c5ec646e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugin disappeared from update center json

[fkpkot]

Hi,
our Plugin (HP-APPLICATION-AUTOMATION-TOOLS) have disappeared from the 
update center json and hosting.

What are the needed steps to restore?

Thanks ahead,
Fima.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ea9e78c9-a70b-40b6-9b20-309061a99b0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin name, Id change

[fkpkot]

Hi,
I've continued the research on this - and why didn't you change the 
repository name? 
It's possible by the organization authorization - or it was disabled at 
that time?

On Sunday, January 1, 2017 at 9:16:25 PM UTC+2, Martin Weber wrote:
>
> Am Samstag, 31. Dezember 2016, 23:08:45 schrieb fkp...@gmail.com 
> : 
> > Hi, 
> > Due to some re-branding issues - we need to change the name of the 
> plugin. 
>
> I renamed the cmakebuilder plugin in 2016. You might want to look at the 
> change history of its pom and the wiki page [1] as a guide. 
>
> Martin 
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/cmakebuilder+Plugin 
>
> -- 
> Cd wrttn wtht vwls s mch trsr. 
>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/233a4bcf-d678-4c5e-9cdd-f1b064a95784%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin name, Id change

[fkpkot]

Thanks!
How about changing the repository name? 
It will require a change on jenkinsci

More of that - will the Jenkins wiki link change if we change only the name?

On Sunday, January 1, 2017 at 11:13:23 AM UTC+2, Baptiste Mathus wrote:
>
> Hello,
>
> Basically, "renaming" a plugin ID does not exist. By that I mean that if 
> you change the artifactId, it's equivalent to create a new plugin. Users 
> won't be able to upgrade. Your stats will restart from 0, and so on. 
>
> You can possibly just adjust the name tag in your pom.xml. It will be 
> visible to end users (after release).
>
> HTH 
>
> Cheers
>
> Le 1 janv. 2017 8:08 AM,  a écrit :
>
>> Hi,
>> Due to some re-branding issues - we need to change the name of the plugin.
>> As far as I know -  I can simply change the POM file. but - 
>>
>>1. What else should i take into consideration? Change?
>>2. which steps should I take prior to POM change? 
>>3. How will it effect The Jira, WIKI and Jenkins plugin stats?
>>
>> If anyone had any experience with this and can spare me the "try and 
>> fail" around this - I'd be happy to hear!
>>
>>
>> Thanks ahead...
>>
>> -- 
>> 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 jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/e2949554-d418-4a19-9b78-853d3fd7c6ec%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/81531a4c-67ed-4dc7-ac31-af5111e886a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugin name, Id change

[fkpkot]

Hi,
Due to some re-branding issues - we need to change the name of the plugin.
As far as I know -  I can simply change the POM file. but - 

   1. What else should i take into consideration? Change?
   2. which steps should I take prior to POM change? 
   3. How will it effect The Jira, WIKI and Jenkins plugin stats?

If anyone had any experience with this and can spare me the "try and fail" 
around this - I'd be happy to hear!


Thanks ahead...

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e2949554-d418-4a19-9b78-853d3fd7c6ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reset wiki cache

[fkpkot]

Is there any way to reset the wiki cache? to avoid the delay time?
I.e. for specific plugin? manually?

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e72291ea-9ff1-4b78-835b-e4e58be2e031%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed builds hide Project action

[fkpkot]

Moreover, sometimes customers will prefer the build to fail after some 
failed load test.

And it seem to affect stage view also (aborted builds).



On Tuesday, November 1, 2016 at 3:54:34 PM UTC+2, Jesse Glick wrote:
>
> On Tue, Nov 1, 2016 at 2:26 AM,   wrote: 
> > I've noticed on my plugin that if all the builds marked as failed than 
> the 
> > project actions won't show up, even though it should be visible since 
> the 
> > file were copied and it failed only due to tests. 
>
> Then you should mark the build unstable, not failed. 
>
> > I've noticed to happen also with TestResultProjectAction of the JUnit 
> > plugin. 
> > 
> > Is it a defect or feature? 
>
> Feature generally. See: 
>
>
> https://github.com/jenkinsci/jenkins/blob/8242e0eb1625454ae5539c444c8d8ecf99a70b62/core/src/main/java/jenkins/tasks/SimpleBuildStep.java#L119-L121
>  
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6f6889f3-1ee6-4c93-b368-d72a2c577e4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Project actions (trend graphs) in pipeline jobs (SimpleBuildStep)

[fkpkot]

Hi,
had the same issue and this is the answer - 
https://groups.google.com/forum/#!topic/jenkinsci-dev/j38TfS6ymJ8

On Wednesday, November 2, 2016 at 1:28:45 AM UTC+2, Ullrich Hafner wrote:
>
> In https://github.com/jenkinsci/warnings-plugin/pull/80 Benjamin is 
> trying to get the trend graphs of the warnings plug-in working for 
> freestyle and pipeline jobs. 
>
> It is almost working now, just one little thing: a trend graph (i.,e,. 
> project action) is not shown for failed builds, see 
>
> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/tasks/SimpleBuildStep.java#L113
>  
> (In the warnings plug-in the project actions methods in a publisher are 
> replaced by implementing SimpleBuildStep) 
>
> This breaks our ATH test 
> WarningsPlugin#should_not_skip_failed_builds_with_option_run_always (good 
> too see that the ATH is quite useful;-) 
>
> There is already a TODO in the source code, what are the plans about this 
> regression (at least for the warnings plugin)? Or is there a workaround 
> available? 
>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f4777a35-fa24-47bf-b508-1a62209b5e97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Replacment for getBuilders()

[fkpkot]

how about job property? how you'd advise to implement it?

On Thursday, October 20, 2016 at 3:27:10 PM UTC+3, Jesse Glick wrote:
>
> On Wed, Oct 19, 2016 at 8:05 PM, Fima  
> wrote: 
> > Do you mean that the pipeline step should return result Into the 
> pipeline 
> > code? And than pass as a parameter for the recorder ? 
>
> That is one option, yes. 
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/eee3ff98-4569-4733-8d7b-bf6d1de7e35c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Replacment for getBuilders()

[fkpkot]

Thanks, 
well I've seen many recorders that relay on getting the builders list in 
order to retrieve their result file (for example - getResultFileName). 
Especially in large plugins they might have several outcomes of result 
files with unique name that's generated during the build.

I understand the design that led for self containment in builders - but in 
recorders, I do think that we should be able to look upon the steps so far 
so we can record their results more easily by getting the correct paths and 
data. (Are their any Jira discussions on this design that I'm missing that 
will shed some light?)

I prefer that the recorder won't search the different nodes for the created 
files - as it will also have be an issue with multi slave pipelines, a 
recorder that set to gather the results and parse them will need to go 
through each slave (i.e. every workspace - if it even possible...). So it 
leaves us with the choice to combine both steps instead of separating them 
as in freestyle build.


Or am I missing something?


On Tuesday, October 18, 2016 at 6:21:13 PM UTC+3, Jesse Glick wrote:
>
> On Tue, Oct 18, 2016 at 9:20 AM,   wrote: 
> > Has anyone found nice workaround which doesn't involve ugly parameter 
> > passing? 
>
> What exactly needs to be worked around? Each step should be 
> self-contained. If it needs to be told where to look for files, tell 
> it. 
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fd298c39-7506-40c2-9cfe-a82adc1096c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Replacment for getBuilders()

[fkpkot]

Hi,
In our plugin we use the getBuilders method in order to learn which 
builders were active during the build and get their working files and etc.
As far as i understand - moving to pipeline has disabled it due to design 
logic (one cannot simply know what went on during the build :) ) and  so 
I'm looking for better solution.

Has anyone found nice workaround which doesn't involve ugly parameter 
passing?

I've been thinking on simply searching for specific result files each run 
but I'm not sure its the best one.


Thanks ahead.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/660556d0-a9cc-452f-98c0-f48368bfe709%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

Please also add the pipeline script you used...

Can be due to the fact you use string as the variable name and when it been 
serached it has some issues?

Could you please upload your jelly view for this  

(If you have a github account to ease this - it will be great..)

On Tuesday, September 27, 2016 at 10:39:21 AM UTC+3, Cédric Cousseran wrote:
>
> Sure, here is the stack trace:
>
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
> failed:
> WorkflowScript: 3: unexpected token: dd3afb84-7f74-4a47-b9da-1cd5ed1cfc59 @ 
> line 3, column 34.
>CustomStep 'dd3afb84-7f74-4a47-b9da-1cd5ed1cfc59'
> ^
>
> 1 error
>
> at 
> org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
> at 
> org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:150)
> at 
> org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:120)
> at 
> org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:132)
> at 
> org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:360)
> at 
> org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:145)
> at 
> org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:111)
> at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:237)
> at 
> org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:167)
> at 
> org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:931)
> at 
> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593)
> at 
> org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569)
> at 
> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546)
> at 
> groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
> at 
> groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
> at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
> at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410)
> at 
> org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373)
> at 
> org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:213)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Finished: FAILURE
>
>
>
> Le lundi 26 septembre 2016 18:02:36 UTC+2, fkp...@gmail.com a écrit :
>>
>> could you please post the stack trace from the console?
>>
>> On Monday, September 26, 2016 at 6:38:55 PM UTC+3, Cédric Cousseran wrote:
>>>
>>> Thanks for the response,
>>>
>>> I took a look at your code, but I've not been able to notice any 
>>> noticeable difference.
>>>
>>> Here is my code, if you have any idea what's wrong in it:
>>>
>>> public class CustomStepExecution extends 
>>> AbstractSynchronousNonBlockingStepExecution {
>>>
>>> private static final long serialVersionUID = 1L;
>>>
>>> @StepContextParameter
>>> private transient TaskListener listener;
>>>
>>> @StepContextParameter
>>> private transient FilePath ws;
>>>
>>> @StepContextParameter
>>> private transient Run build;
>>>
>>> @StepContextParameter
>>> private transient Launcher launcher;
>>>
>>> @Inject
>>> private transient CustomStep step;
>>>
>>> @Override
>>> protected Void run() {
>>>//work
>>> return null;
>>> }
>>> }
>>>
>>>
>>>
>>> public class CustomStep extends AbstractStepImpl {
>>>
>>> private final String string;
>>>
>>> public String getString() {
>>> return string;
>>> }
>>>
>>> @DataBoundConstructor
>>> public CustomStep(@Nonnull String string) {
>>> this.string = string
>>> }
>>>
>>> @Extension
>>> public static class DescriptorImpl extends AbstractStepDescriptorImpl {
>>>
>>> public DescriptorImpl() {
>>> super(CustomStepExecution.class);
>>> }
>>>
>>> @Override
>>> public String getFunctionName() {
>>> return "CustomStep";
>>> }
>>>
>>> @Nonnull
>>> @Override
>>> public String getDisplayName() {
>>> return "Launch Step";
>>> }
>>> }
>>> }
>>>
>>>
>>>
>>>
>>> Le lundi 26 septembre 2016 15:53:48 UTC+2, fkp...@gmail.com a écrit :

 If you'd publish some link to your code - I could take a look and see 
 if there's any fix i made that can be relevant for your plugin.

 You can also compare here to see if you spot any differences (it's 

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

could you please post the stack trace from the console?

On Monday, September 26, 2016 at 6:38:55 PM UTC+3, Cédric Cousseran wrote:
>
> Thanks for the response,
>
> I took a look at your code, but I've not been able to notice any 
> noticeable difference.
>
> Here is my code, if you have any idea what's wrong in it:
>
> public class CustomStepExecution extends 
> AbstractSynchronousNonBlockingStepExecution {
>
> private static final long serialVersionUID = 1L;
>
> @StepContextParameter
> private transient TaskListener listener;
>
> @StepContextParameter
> private transient FilePath ws;
>
> @StepContextParameter
> private transient Run build;
>
> @StepContextParameter
> private transient Launcher launcher;
>
> @Inject
> private transient CustomStep step;
>
> @Override
> protected Void run() {
>//work
> return null;
> }
> }
>
>
>
> public class CustomStep extends AbstractStepImpl {
>
> private final String string;
>
> public String getString() {
> return string;
> }
>
> @DataBoundConstructor
> public CustomStep(@Nonnull String string) {
> this.string = string
> }
>
> @Extension
> public static class DescriptorImpl extends AbstractStepDescriptorImpl {
>
> public DescriptorImpl() {
> super(CustomStepExecution.class);
> }
>
> @Override
> public String getFunctionName() {
> return "CustomStep";
> }
>
> @Nonnull
> @Override
> public String getDisplayName() {
> return "Launch Step";
> }
> }
> }
>
>
>
>
> Le lundi 26 septembre 2016 15:53:48 UTC+2, fkp...@gmail.com a écrit :
>>
>> If you'd publish some link to your code - I could take a look and see if 
>> there's any fix i made that can be relevant for your plugin.
>>
>> You can also compare here to see if you spot any differences (it's in 
>> ongoing work following the comments I got from Jesse but it works)
>>
>> https://github.com/YafimK/hp-application-automation-tools-plugin/tree/LoadRunnerPipelineStep/src/main/java/com/hp/application/automation/tools/pipelineSteps
>>  
>> 
>>
>> On Monday, September 26, 2016 at 4:13:54 PM UTC+3, Cédric Cousseran wrote:
>>>
>>> Hi,
>>>
>>> I've encountered the same issue with my plugin, the syntax of the 
>>> snippet generator is not supported.
>>> I've tried the solutions you mentioned, without success.
>>> Do you have a more precise idea of what caused your issue?
>>>
>>> Thanks,
>>> Cédric Cousseran
>>>
>>>
>>> Le jeudi 1 septembre 2016 14:53:45 UTC+2, Fima a écrit :

 Saw that, but I couldn't find what you've said about the Flow Node... 
 I guess I'll look at the code.


 On Thu, Sep 1, 2016 at 1:54 PM, Jesse Glick  
 wrote:

>
> https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md
>  
> has some information though it probably needs more. 
> https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md 
> is the landing page.
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/34AKdC0SARM/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3c_mY3enmY6jJNFMAiTsOwX55PKxLO6E2vR0Bo4Csf3Q%40mail.gmail.com
>  
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ee1b7fd3-fdc9-4703-bc2d-e1393a573448%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compatability with parallel

[fkpkot]

Thanks!
Yes, I still can't trace the source, I need to inspect threads more 
carefully to try to catch it.
Are there any methods that i need to look into - given the below exceptions?


PM org.jenkinsci.plugins.workflow.cps.CpsStepContext onFailure
WARNING: already completed CpsStepContext[30]:Owner[new pipe test/5:new 
pipe test #5]
java.lang.IllegalStateException: 
org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
at 
org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(CpsStepContext.java:325)
at 
org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$Wrapper.onFailure(BodyExecutionCallback.java:89)
at 
org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:278)
at 
com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68)
at 
com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
at 
org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:324)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224)
at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
at 
org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:382)
at 
org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:362)
at 
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:627)
at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
... 8 more
Caused by: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
at 
org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.cancel(CpsBodyExecution.java:189)
at 
org.jenkinsci.plugins.workflow.steps.BodyExecution.cancel(BodyExecution.java:76)
at 
org.jenkinsci.plugins.workflow.cps.steps.ParallelStepExecution.stop(ParallelStepExecution.java:66)
at 
org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:144)
at 
org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:131)
at 
org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:278)
at 
com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68)
at 
com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
at 
org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:324)
at 

Re: Compatability with parallel

[fkpkot]

Thanks for the answer!
Currently, I can't seem to pinpoint the exact issue when it crashes and I'm 
still thinking of the appropriate way to debug it.

Maybe it's due to the fact that I'm using Abstract Sync non block step? 
instead of the ASync one? although I don't see that as an issue.

PM org.jenkinsci.plugins.workflow.cps.CpsStepContext onFailure
WARNING: already completed CpsStepContext[30]:Owner[new pipe test/5:new 
pipe test #5]
java.lang.IllegalStateException: org.jenkinsci.plugins.workflow.steps.
FlowInterruptedException
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.onFailure(
CpsStepContext.java:325)
at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$Wrapper.
onFailure(BodyExecutionCallback.java:89)
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.
receive(CpsBodyExecution.java:278)
at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68
)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:
21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(
SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(
SandboxContinuable.java:33)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(
SandboxContinuable.java:30)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.
runInSandbox(GroovySandbox.java:108)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(
SandboxContinuable.java:30)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.
java:163)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.
java:324)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(
CpsThreadGroup.java:78)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(
CpsThreadGroup.java:236)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(
CpsThreadGroup.java:224)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(
CpsVmExecutorService.java:63)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(
SingleLaneExecutorService.java:112)
at jenkins.util.ContextResettingExecutorService$1.run(
ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(
CpsStepContext.java:382)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(
CpsStepContext.java:362)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(
CpsFlowExecution.java:627)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(
CpsVmExecutorService.java:35)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
511)
... 8 more
Caused by: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.cancel(
CpsBodyExecution.java:189)
at org.jenkinsci.plugins.workflow.steps.BodyExecution.cancel(
BodyExecution.java:76)
at org.jenkinsci.plugins.workflow.cps.steps.ParallelStepExecution.stop(
ParallelStepExecution.java:66)
at org.jenkinsci.plugins.workflow.cps.steps.
ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:144)
at org.jenkinsci.plugins.workflow.cps.steps.
ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:131)
at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.
receive(CpsBodyExecution.java:278)
at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68
)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:
21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(
SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(
SandboxContinuable.java:33)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(
SandboxContinuable.java:30)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.
runInSandbox(GroovySandbox.java:108)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(
SandboxContinuable.java:30)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.
java:163)
at 

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

If you'd publish some link to your code - I could take a look and see if 
there's any fix i made that can be relevant for your plugin.

You can also compare here to see if you spot any differences (it's in 
ongoing work following the comments I got from Jesse but it works)
https://github.com/YafimK/hp-application-automation-tools-plugin/tree/LoadRunnerPipelineStep/src/main/java/com/hp/application/automation/tools/pipelineSteps

On Monday, September 26, 2016 at 4:13:54 PM UTC+3, Cédric Cousseran wrote:
>
> Hi,
>
> I've encountered the same issue with my plugin, the syntax of the snippet 
> generator is not supported.
> I've tried the solutions you mentioned, without success.
> Do you have a more precise idea of what caused your issue?
>
> Thanks,
> Cédric Cousseran
>
>
> Le jeudi 1 septembre 2016 14:53:45 UTC+2, Fima a écrit :
>>
>> Saw that, but I couldn't find what you've said about the Flow Node... 
>> I guess I'll look at the code.
>>
>>
>> On Thu, Sep 1, 2016 at 1:54 PM, Jesse Glick  wrote:
>>
>>>
>>> https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md 
>>> has some information though it probably needs more. 
>>> https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md is 
>>> the landing page.
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/34AKdC0SARM/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3c_mY3enmY6jJNFMAiTsOwX55PKxLO6E2vR0Bo4Csf3Q%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c4d243ab-445d-4caf-ad96-4420ba3dc81e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Compatability with parallel

[fkpkot]

Hi,
I'd like our plugin to support the parallel step (in pipelines).
I haven't found any documentation on what steps / methods i should 
implement to ensure our support.

Is there any known issues / methods or etc. i should go through?

Thanks ahead!

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0d22e785-9c99-43c9-9c5a-9bae22576a33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jenkins jira] is there a way to connect a plugin jira account to slack?

[fkpkot]

Hi,
I'd like to connect a dev group on slack to the jira of the plugin on 
jenkin-ci.org.
In the official configuration of the slack integration i need to define the 
web hook in jira - is it available to plugin owners / maintainers at 
jenkins-ci jira ?

Thanks ahead

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7ca5e9bf-26a4-4f51-848f-e827ce337ee7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

1. Well, your points might lead to tedious refactoring of old code and 
design :)
 but in short, the removal of the possibility (in the new Project-job 
model) to check the list of previous builders used is the main issue which 
led for this. 

Since it's not convenient to start looking for which files were created 
during the builders run. for example if four different builders of my 
plugin ran and each have created it's result, I'd have to look for each 
possible result file and parse it - instead of simply "pulling" it from the 
builder - which is much simpler.

2. I will look into that. I've been thinking on the need to shift for the 
asyncrhonous due to step length concern mainly.

3. Where can I read the DOC on the advanced API (such as the one you 
mentioned...) - other then looking straight at the code (which is cool, but 
is there something else? )

Thanks again!  


On Wednesday, August 31, 2016 at 5:23:26 PM UTC+3, Jesse Glick wrote:
>
> On Wed, Aug 31, 2016 at 8:59 AM,   wrote: 
> > it's 
> > better to separate it - especially when you have a builder and recorder 
> in 
> > one plugin and you'd like to make it a one step in pipeline. 
>
> If there is a reason for these to be separate in a freestyle project, 
> why should a Pipeline script be obliged to run both in conjunction? 
>
> > In what cases it's advised to separate? and not share code? 
>
> · you need to write an asynchronous step 
> · you need to use some more advanced Pipeline APIs (e.g., adding an 
> `Action` to a `FlowNode`) 
> · there is no way the current `SimpleBuildStep`/`SimpleBuildWrapper` 
> databinding could work sensibly in a Pipeline script 
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/24acf97c-e447-4da6-a1cf-d7575589becf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

hmmm ...
as i've understood from the posted refactoring guide on Jenkins.io, it's 
better to separate it - especially when you have a builder and recorder in 
one plugin and you'd like to make it a one step in pipeline.
I've also looked at HtmlPublisher that separated too.

In what cases it's advised to separate? and not share code? i.e. create 
diffrent module to support pipeline that launches modules of freestyle 
job..?


On Tuesday, August 30, 2016 at 11:26:38 AM UTC+3, Jesse Glick wrote:
>
> Not clear why you are writing a `Step` at all. From a quick glance, you 
> could just implement `SimpleBuildStep` on an existing `Builder` or 
> `Publisher` and share more code with freestyle. Assuming there is a 
> `@Symbol`, the result will look just like a true `Step`.
>
> A `@Symbol` should start with a lowercase letter.
>
> Use `@DataBoundSetter` for optional parameters.
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2aafb933-4843-4092-83b1-0f5a079719ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

Thanks,
You're right, it didn't sound right but it worked.I've checked it again and 
probably something else? maybe just adding the structs dependency solved 
it? e
[added the code -  just a trial and error experience ]

public class LrScenarioLoadStep extends AbstractStepImpl {

public String getArchiveRunTestResultsMode() {
//return archiveRunTestResultsMode;
return ResultsPublisherModel.CreateHtmlReportResults.toString();
}

public boolean isPublishResults() {
//return publishResults;
return true;
}

public String getIgnoreErrorStrings() {
return ignoreErrorStrings;
}

public String getPerScenarioRunTimeOut() {
return perScenarioRunTimeOut;
}

public String getControllerRunPollingInterval() {
return controllerRunPollingInterval;
}

public String getRunTimeout() {
return runTimeout;
}

public String getTestPaths() {
return testPaths;
}

private final  String archiveRunTestResultsMode;
private final  boolean publishResults;
private final  String ignoreErrorStrings;
private final  String perScenarioRunTimeOut;
private final  String controllerRunPollingInterval;
private final  String runTimeout;
private final  String testPaths;



@DataBoundConstructor
public LrScenarioLoadStep( String runTimeout, String ignoreErrorStrings, 
String perScenarioRunTimeOut, String controllerRunPollingInterval, String 
testPaths)
{
this.testPaths = testPaths;
this.runTimeout = runTimeout;
this.controllerRunPollingInterval = controllerRunPollingInterval;
this.perScenarioRunTimeOut = perScenarioRunTimeOut;
this.ignoreErrorStrings = ignoreErrorStrings;
}

@Extension @Symbol("LrScenarioLoad")
public static class DescriptorImpl extends AbstractStepDescriptorImpl {
public DescriptorImpl() { super(LrScenarioLoadStepExecution.class); }

@Override
public String getFunctionName() {
return "lrScenarioLoad";
}

@Nonnull
@Override
public String getDisplayName() {
return "Run LoadRunner scenario";
}

public List getReportArchiveModes() {

return ResultsPublisherModel.archiveModes;
}


}

}


and the executor:

public class LrScenarioLoadStepExecution extends 
AbstractSynchronousNonBlockingStepExecution {

@Inject
private transient LrScenarioLoadStep step;

@StepContextParameter
private transient TaskListener listener;

@StepContextParameter
private transient FilePath ws;

@StepContextParameter
private transient Run build;

@StepContextParameter
private transient Launcher launcher;



@Override
protected Void run() throws Exception {

RunFromFileBuilder runFromFileBuilder = new 
RunFromFileBuilder(step.getTestPaths(), step.getRunTimeout(), 
step.getControllerRunPollingInterval(), step.getPerScenarioRunTimeOut(), 
step.getIgnoreErrorStrings(), "", "", "", "", "", "", "", "", "", "", "", "", 
"", null, false);
RunResultRecorder runResultRecorder = new 
RunResultRecorder(step.isPublishResults(), step.getArchiveRunTestResultsMode());
runFromFileBuilder.perform(build, ws, launcher, listener);

HashMap resultFilename = new HashMap(0);
resultFilename.put(RunFromFileBuilder.class.getName(), 
runFromFileBuilder.getRunResultsFileName());

runResultRecorder.pipelinePerform(build, ws, launcher, listener, 
resultFilename);

return null;
}

private static final long serialVersionUID = 1L;
}



On Monday, August 29, 2016 at 9:49:13 PM UTC+3, Jesse Glick wrote:
>
> On Mon, Aug 29, 2016 at 4:15 AM,   wrote: 
> > Solved by following 
> > https://wiki.jenkins-ci.org/display/JENKINS/Structs+plugin and changing 
> the 
> > order of variables in the Constructor. 
>
> Order of variables in a constructor should not matter, so perhaps you 
> are doing something else wrong. Without a self-contained code example 
> it is hard to say. 
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/29207259-7fd1-4725-bb1d-e1c9437d8a15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding pipeline compatabilty to jenkins plugin

[fkpkot]

Solved by following *https://wiki.jenkins-ci.org/display/JENKINS/Structs+plugin 
 *and changing 
the order of variables in the Constructor.

On Sunday, August 28, 2016 at 6:40:32 PM UTC+3, fkp...@gmail.com wrote:
>
> Hi,
> I followed the nice guide on refactoring my Jenkins plugin to pipeline 
> compatibility given at Jenkins.io.
> I've stumbled on a strange issue - the snippet generator creates the 
> groovy syntax but without parenthesis and without brackets, which is ok 
> since groovy does support it.
>
> But once i paste in at my job DSL he writes "Unexpected token: "one of the 
> tags" ", if i add the brackets manually - it works!
>
> another small issue i've noticed while debugging is that it calls the 
> Class extending "AbstractStepImpl" twice - but I'm not sure it's related...
>
> the code is here:
>
> https://github.com/YafimK/hp-application-automation-tools-plugin/tree/LoadRunnerPipelineStep/src/main/java/com/hp/application/automation/tools/pipelineSteps
>
> that's my current dependency list:
>
> 
>  org.jenkins-ci.plugins.workflow
>  workflow-step-api
>  ${workflow.version}
> 
>  
>  org.jenkins-ci.plugins.workflow
>  workflow-step-api
>  ${workflow.version}
>  tests
>  test
> 
> 
>  org.jenkins-ci.plugins.workflow
>  workflow-aggregator
>  ${workflow.version}
>  test
> 
> 
>  org.jenkins-ci.plugins.workflow
>  workflow-cps
>  ${workflow.version}
> 
>
>
> and I'm building with 1.642.4 as baseline and parent POM...
>
> Is there any known issue or any solution that i've missed (i tried to look 
> at HTML publisher, junit archiver and artifict archiver as reference) ?
>
> Thanks ahead,
> Fima.
>  
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/64548efb-d2a6-427f-8cc3-aebec3c97096%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Adding pipeline compatabilty to jenkins plugin

[fkpkot]

Hi,
I followed the nice guide on refactoring my Jenkins plugin to pipeline 
compatibility given at Jenkins.io.
I've stumbled on a strange issue - the snippet generator creates the groovy 
syntax but without parenthesis and without brackets, which is ok since 
groovy does support it.

But once i paste in at my job DSL he writes "Unexpected token: "one of the 
tags" ", if i add the brackets manually - it works!

another small issue i've noticed while debugging is that it calls the Class 
extending "AbstractStepImpl" twice - but I'm not sure it's related...

the code is here:
https://github.com/YafimK/hp-application-automation-tools-plugin/tree/LoadRunnerPipelineStep/src/main/java/com/hp/application/automation/tools/pipelineSteps

that's my current dependency list:


 org.jenkins-ci.plugins.workflow
 workflow-step-api
 ${workflow.version}

 
 org.jenkins-ci.plugins.workflow
 workflow-step-api
 ${workflow.version}
 tests
 test


 org.jenkins-ci.plugins.workflow
 workflow-aggregator
 ${workflow.version}
 test


 org.jenkins-ci.plugins.workflow
 workflow-cps
 ${workflow.version}



and I'm building with 1.642.4 as baseline and parent POM...

Is there any known issue or any solution that i've missed (i tried to look 
at HTML publisher, junit archiver and artifict archiver as reference) ?

Thanks ahead,
Fima.
 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/00d6b7f4-58f9-4054-8ddd-0913c08bb407%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Would a plugin built for regular Jenkisn work on CloudBees jenkins

[fkpkot]

Hi,
I'm working on the hp automation tools plugin, and i wanted to ask if there 
would there be any issues in a plugin built against a regular version of 
Jenkins 1.x / 2.x used on CloudBees enterprise Jenkins?
I guess the plugin development should cover both ...  

but I'd like to be sure, has anyone ever encountered issues in such 
environments?

Thanks ahead,
Fima.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f54a560c-790a-44ee-aafc-da68b78a0f2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interested in building your plugin on ci.jenkins.io?

[fkpkot]

Hi,
will there be any support for Xbuild ? so that a combined java & c# plugin 
can be built?

if so, I'd like the hp automation tools plugin to be built on that and i'll 
write the Jenkinsfile.

thanks
Fima.

On Monday, August 8, 2016 at 6:48:24 PM UTC+3, R Tyler Croy wrote:
>
> Howdy there, your friendly project infrastructure dude here. I'm hoping to 
> get 
> more accurate usage requirements for our eventual migration of 
> https://ci.jenkins.io, and the rest of our infra, to Azure [0]. If your 
> plugin 
> repository already has a `Jenkinsfile`, or you're interested in creating 
> one 
> for your plugin, I would love to have your plugin built on our existing 
> Jenkins-on-Jenkins. 
>
>
> We already have a couple plugins [1] being built on ci.jenkins.io, but I 
> need 
> more! 
>
>
> If you're interested in having your plugin built and/or helping out, 
> please 
> reply or ping me (rtyler) in the #jenkins-infra channel. 
>
>
>
> [0] https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/ 
> [1] https://ci.jenkins.io/job/Plugins/ 
>
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F 
> -- 
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9f0516bf-cc9c-4ff9-bbb5-586e18f1271a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [plugin dev][Cloudbees build service] failed build due to usage of msbuild in pom in Jenkinsci repo

[fkpkot]

does anyone has an idea how to change the build template that is used? or 
how to customize our pom to support it?

On Tuesday, July 19, 2016 at 3:18:01 PM UTC+3, fkp...@gmail.com wrote:
>
> Hi,
> i've noticed that the regular Jenkins build of our plugin on the cloudbees 
> service for Jenkins CI fails.
> I guess the issue is due to Jenkins node based on Linux while the pom 
> requires windows path for .Net framework files.
>
> What's the best solution for cases such as this?
>
> I'm attaching the build log.
>
> The errors can be seen at the end - 
>
>> ERROR] Failed to execute goal 
>> org.codehaus.mojo:exec-maven-plugin:1.4.0:exec (clean
>> HPToolsLauncher) on project hp-application-automation-tools-plugin: 
>> Command execution
>> failed. Cannot run program 
>> "C:/Windows/Microsoft.NET/Framework/v4.0.30319/msbuild.exe"
>> (in directory 
>> "/scratch/jenkins/workspace/plugins/hp-application-automation-toolsplugin/
>> HpToolsLauncher"): error=2, No such file or directory -> [Help 1]
>>
>
> the link to the build is:
>
> https://jenkins.ci.cloudbees.com/job/plugins/job/hp-application-automation-tools-plugin/
>
> (it compiles well on our windows based build Jenkins nodes) 
>
> Thanks ahead,
> Fima.
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6d8f22f0-cb85-45af-b137-970852bdf14d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[plugin hosting]

[fkpkot]

Hi,
I have proper commit rights to the Jenkinsci repository of my plugin - but 
I'm not listed in the maintainer list on the plugin page on jenkins.io.
Could I still make release to the plugin repository with Jenkins jira 
account or ill have to use another maintainer's account?

Thanks ahead'
fima

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/70ec35d9-0a62-4e1f-9bd6-2d25f94b0eca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Plugin Hosting] Updating JenkinsCI plugin repo with external Github repo

[fkpkot]

Hi,
I'm the new maintainer of the HP plugin and i'd like to update the current 
jenkins repo of our plugin to the correct version that exists in our github 
repo.
What should i do to accomplish that?

Can i make a double deploy to the plugin to both repo's?

Currently i can't create proper pull request to update the JenkinsCI HP 
plugin repo due to it's being serious out of sync with ours.

Thanks ahead.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7d77c6f1-ca56-4847-90d9-056bb7940876%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Changing plugin version

[fkpkot]

Hi,
Strange issue ahead warning...
Our plugin needs a version change - i.e were currently at version 3.0.8 but 
due to Jenkins 2, i'd want to change it to 1.3.0.8 ~~ 
The problem is that i understand it will create problem with downgrading 
for users - 
did anyone found any smart solutions for this matter?

Thanks ahead.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/385d1278-0eb2-46aa-9040-0e945f78bc97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[plugin-dev] [BlueOcean] Adding Plot / Graph to existant plugin

[fkpkot]

Hi,
 i want to add support for graphs and plots in my plugin - but I'm not sure 
if to start working on graphing libraries in reactJS to support the 
upcoming blueocean ui 
or instead i should work on adopting the plot plugin and adding it to my 
plugin somehow


any help or direction will or gratefully accepted =)

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/88e2d211-85b7-41ac-8652-c75ec1c8539c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean]

[fkpkot]

Hi,
Working on my jenkins plugin and i'd be glad to hear if there's any clear 
release schedule for the plugin.
I'm trying to asses the time and effort to adapt our plugin to support this 
cool plugin - 
 

Is there anything like that? i haven't found it till now (i know about the 
jira but i seek something more clear than list of issues to help the 
assessment)


Thanks ahead.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e2a98d13-393e-4133-a703-dc0b4dbb2219%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkpkot]

Thanks! that worked. although i still can't simply press run on my pipeline 
in order to run  - and i have to go to the old interface to do it.
I'm having some kind of exception on symbolic link - could that be the 
issue?

On Tuesday, June 14, 2016 at 10:28:40 AM UTC+3, Tom Fennelly wrote:
>
> As said earlier  you will have a job if you are not running via 
> hpi:run. You will need to gather and install more than just the blueocean 
> plugins.
>
> You could use "mvn hpi:assemble-dependencies" to pull together all of the 
> plugins you need. You'd need to run this inside blueocean-plugin/
> blueocean-plugin.
>
> On 14 June 2016 at 14:57,  wrote:
>
>> Very partly by installing HPI's manually - but only some of the 
>> functionalities worked (but without any errors)
>>
>>
>> On Tuesday, June 14, 2016 at 8:14:44 AM UTC+3, Michael Neale wrote:
>>>
>>> You said you had it working previously? 
>>>
>>> On Tuesday, June 14, 2016 at 3:08:38 PM UTC+10, fkp...@gmail.com wrote:

 Thanks - but i'm still having strange difficulties runningthe plugin 
 similar to the Win 7 issues that were discussed previously.

 i'm adding my screen logs - after several retries to reinstall the 
 plugin (is it fit to run behind a corporate proxy? maybe that's the cause 
 to all the problems) - and now it simply won't run.

 be glad for any help.


 On Tuesday, June 14, 2016 at 6:51:55 AM UTC+3, Michael Neale wrote:
>
> Hey - that's cool!
>
> There is no "create pipeline" feature yet in blue ocean, hence it 
> takes you to the classic UI. 
>
> For building plugins, 
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin 
> is a sample plugin that you can look at. 
> What is the plugin you are interested? many plugins will need to have 
> the right extension point added in blue ocean which may not already be 
> there. 
>
> On Tuesday, June 14, 2016 at 1:15:13 AM UTC+10, fkp...@gmail.com 
> wrote:
>>
>> Finally succeed installing it on the machine after reinstalling with 
>> jenkins 2.8.
>> But couldn't use mvn run:hpi - >> installed all the plugins manually 
>> from the folder with upload and then ran it. and it works =)
>> Now the (great) ui works - but when i press new pipeline - it takes 
>> me to the old screen - is it ok?
>>
>> Starting to check compatability between our plugin to the new UI - 
>> any suggestions as where should i start the conversion? and how?
>>  
>>
>> On Friday, June 10, 2016 at 6:44:30 PM UTC+3, fkp...@gmail.com wrote:
>>>
>>> Hi,
>>> tried to compile the project to start testing related plugins on the 
>>> project ui.
>>> related tool versions:
>>>
>>>1. maven 3.3.9
>>>2. jenkins 2.8 (latest release) - tried also with stable lts 
>>>1.651.2 (same problems).
>>>
>>> attaching the build log after several retries, I read the past 
>>> thread on win 7 issues but it seems as a different problem.
>>>
>>>
>>>
>>> Thanks ahead,
>>>
>>> Yafim.
>>>
>>>
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/1A82YO-Ta2w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/d05496c8-f66b-42e1-acb7-42790dbddf71%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9c3c118b-acfd-4eda-8510-2be0935b5f6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkpkot]

Very partly by installing HPI's manually - but only some of the 
functionalities worked (but without any errors)

On Tuesday, June 14, 2016 at 8:14:44 AM UTC+3, Michael Neale wrote:
>
> You said you had it working previously? 
>
> On Tuesday, June 14, 2016 at 3:08:38 PM UTC+10, fkp...@gmail.com wrote:
>>
>> Thanks - but i'm still having strange difficulties runningthe plugin 
>> similar to the Win 7 issues that were discussed previously.
>>
>> i'm adding my screen logs - after several retries to reinstall the plugin 
>> (is it fit to run behind a corporate proxy? maybe that's the cause to all 
>> the problems) - and now it simply won't run.
>>
>> be glad for any help.
>>
>>
>> On Tuesday, June 14, 2016 at 6:51:55 AM UTC+3, Michael Neale wrote:
>>>
>>> Hey - that's cool!
>>>
>>> There is no "create pipeline" feature yet in blue ocean, hence it takes 
>>> you to the classic UI. 
>>>
>>> For building plugins, 
>>> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin 
>>> is a sample plugin that you can look at. 
>>> What is the plugin you are interested? many plugins will need to have 
>>> the right extension point added in blue ocean which may not already be 
>>> there. 
>>>
>>> On Tuesday, June 14, 2016 at 1:15:13 AM UTC+10, fkp...@gmail.com wrote:

 Finally succeed installing it on the machine after reinstalling with 
 jenkins 2.8.
 But couldn't use mvn run:hpi - >> installed all the plugins manually 
 from the folder with upload and then ran it. and it works =)
 Now the (great) ui works - but when i press new pipeline - it takes me 
 to the old screen - is it ok?

 Starting to check compatability between our plugin to the new UI - any 
 suggestions as where should i start the conversion? and how?
  

 On Friday, June 10, 2016 at 6:44:30 PM UTC+3, fkp...@gmail.com wrote:
>
> Hi,
> tried to compile the project to start testing related plugins on the 
> project ui.
> related tool versions:
>
>1. maven 3.3.9
>2. jenkins 2.8 (latest release) - tried also with stable lts 
>1.651.2 (same problems).
>
> attaching the build log after several retries, I read the past thread 
> on win 7 issues but it seems as a different problem.
>
>
>
> Thanks ahead,
>
> Yafim.
>
>
>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d05496c8-f66b-42e1-acb7-42790dbddf71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkpkot]

Finally succeed installing it on the machine after reinstalling with 
jenkins 2.8.
But couldn't use mvn run:hpi - >> installed all the plugins manually from 
the folder with upload and then ran it. and it works =)
Now the (great) ui works - but when i press new pipeline - it takes me to 
the old screen - is it ok?

Starting to check compatability between our plugin to the new UI - any 
suggestions as where should i start the conversion? and how?
 

On Friday, June 10, 2016 at 6:44:30 PM UTC+3, fkp...@gmail.com wrote:
>
> Hi,
> tried to compile the project to start testing related plugins on the 
> project ui.
> related tool versions:
>
>1. maven 3.3.9
>2. jenkins 2.8 (latest release) - tried also with stable lts 1.651.2 
>(same problems).
>
> attaching the build log after several retries, I read the past thread on 
> win 7 issues but it seems as a different problem.
>
>
>
> Thanks ahead,
>
> Yafim.
>
>
>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0c253964-d9c5-44a0-885e-b42b3d7dd393%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkpkot]

Hi,
Thanks for the speedy reply.

It is an html file stating that i should check my proxy settings which are 
defined in the .m2/settings.xml.
I'm trying to reimport it currently as i checked the connection to the 
proxy and it should be fine (otherwise all the other dependencies won't be 
downloaded as well - i guess).


On Friday, June 10, 2016 at 8:01:28 PM UTC+3, Cliff Meyers wrote:
>
> Hi,
>
> I am not 100% sure at the root issue but can you check the contents of the 
> following file?  C:\Users\kazaky\.m2\repository\org\jenkins-ci\
> plugins\plugin\2.2\plugin-2.2.pom
>
> From the parser error the file appears to be an HTML document but should 
> be a fairly long XML file. There may have been an issue downloading that 
> file from the repo. Perhaps the contents will offer a clue.
>
> Also, do you have any special repo config in your ~/.m2/settings.xml file?
>
> -Cliff
>
>
> On Fri, Jun 10, 2016 at 12:30 PM,  wrote:
>
>> concrete errors output with -e -X flags
>>
>> [ERROR] Failed to execute goal 
>> org.jenkins-ci.tools:maven-hpi-plugin:1.117:test-hpl (default-test-hpl) on 
>> project blueocean: Error preparing the manifest: Failed to open artifact 
>> org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at 
>> C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar:
>>  
>> 1 problem was encountered while building the effective model for 
>> org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
>> [ERROR] [FATAL] Non-parseable POM 
>> C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom:
>>  
>> end tag name  must be the same as start tag  from line 4 
>> (position: TEXT seen ...\n  ... @66:10)  @ 
>> C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom,
>>  
>> line 66, column 10
>> [ERROR] for project 
>> org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version] for 
>> project org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
>> [ERROR] -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
>> goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:test-hpl 
>> (default-test-hpl) on project blueocean: Error preparing the manifest: 
>> Failed to open artifact 
>> org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at 
>> C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
>> at 
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>> at 
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at 
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at 
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>> at 
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>> at 
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at 
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at 
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at 
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at 
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at 
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error 
>> preparing the manifest: Failed to open artifact 
>> org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at 
>> C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
>> at org.jenkinsci.maven.plugins.hpi.HplMojo.execute(HplMojo.java:108)
>> at 
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at 
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>> ... 20 more
>> Caused by: 

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkpkot]

concrete errors output with -e -X flags

[ERROR] Failed to execute goal 
org.jenkins-ci.tools:maven-hpi-plugin:1.117:test-hpl (default-test-hpl) on 
project blueocean: Error preparing the manifest: Failed to open artifact 
org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar:
 
1 problem was encountered while building the effective model for 
org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
[ERROR] [FATAL] Non-parseable POM 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom:
 
end tag name  must be the same as start tag  from line 4 
(position: TEXT seen ...\n  ... @66:10)  @ 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom,
 
line 66, column 10
[ERROR] for project 
org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version] for 
project org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:test-hpl 
(default-test-hpl) on project blueocean: Error preparing the manifest: 
Failed to open artifact 
org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error preparing 
the manifest: Failed to open artifact 
org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
at org.jenkinsci.maven.plugins.hpi.HplMojo.execute(HplMojo.java:108)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: org.kohsuke.stapler.framework.io.IOException2: Failed to open 
artifact org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile 
at 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
at 
org.jenkinsci.maven.plugins.hpi.MavenArtifact.getResolvedType(MavenArtifact.java:172)
at 
org.jenkinsci.maven.plugins.hpi.MavenArtifact.isPlugin(MavenArtifact.java:55)
at 
org.jenkinsci.maven.plugins.hpi.HplMojo.buildLibraries(HplMojo.java:128)
at org.jenkinsci.maven.plugins.hpi.HplMojo.execute(HplMojo.java:96)
... 22 more
Caused by: org.apache.maven.project.InvalidProjectModelException: 1 problem 
was encountered while building the effective model for 
org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
[FATAL] Non-parseable POM 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom:
 
end tag name  must be the same as start tag  from line 4 
(position: TEXT seen ...\n  ... @66:10)  @ 
C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom,
 
line 66, column 10
 for project 

[Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkpkot]

Hi,
tried to compile the project to start testing related plugins on the 
project ui.
related tool versions:

   1. maven 3.3.9
   2. jenkins 2.8 (latest release) - tried also with stable lts 1.651.2 
   (same problems).

attaching the build log after several retries, I read the past thread on 
win 7 issues but it seems as a different problem.



Thanks ahead,

Yafim.




-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4aa37590-91ef-41b5-af96-8a4a7285e6e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Blue Ocean UI Parent
[INFO] BlueOcean :: Commons API
[INFO] BlueOcean :: Web module
[INFO] BlueOcean :: Rest module
[INFO] BlueOcean :: Dashboard
[INFO] BlueOcean :: REST API implementation
[INFO] BlueOcean :: Aggregator
[INFO] 
[INFO] 
[INFO] Building Blue Ocean UI Parent 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.6:clean (default-clean) @ blueocean-parent ---
[INFO] Deleting c:\JenkinsPlugs\blueocean-plugin\target
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:display-info (display-info) @ 
blueocean-parent ---
[INFO] Maven Version: 3.3.9
[INFO] JDK Version: 1.8.0_91 normalized as: 1.8.0-91
[INFO] OS Info: Arch: amd64 Family: dos Name: windows 10 Version: 10.0
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (display-info) @ 
blueocean-parent ---
[INFO] 
[INFO] --- maven-localizer-plugin:1.23:generate (default) @ blueocean-parent ---
[INFO] 
[INFO] >>> maven-javadoc-plugin:2.10.1:javadoc (default) > generate-sources @ 
blueocean-parent >>>
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:display-info (display-info) @ 
blueocean-parent ---
[INFO] Maven Version: 3.3.9
[INFO] JDK Version: 1.8.0_91 normalized as: 1.8.0-91
[INFO] OS Info: Arch: amd64 Family: dos Name: windows 10 Version: 10.0
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (display-info) @ 
blueocean-parent ---
[INFO] 
[INFO] --- maven-localizer-plugin:1.23:generate (default) @ blueocean-parent ---
[INFO] 
[INFO] <<< maven-javadoc-plugin:2.10.1:javadoc (default) < generate-sources @ 
blueocean-parent <<<
[INFO] 
[INFO] --- maven-javadoc-plugin:2.10.1:javadoc (default) @ blueocean-parent ---
[INFO] Skipping javadoc generation
[INFO] 
[INFO] --- animal-sniffer-maven-plugin:1.14:check (check) @ blueocean-parent ---
[INFO] Signature checking is skipped.
[INFO] 
[INFO] --- gmaven-plugin:1.5-jenkins-3:generateTestStubs (test-in-groovy) @ 
blueocean-parent ---
[INFO] No sources found for Java stub generation
[INFO] 
[INFO] --- gmaven-plugin:1.5-jenkins-3:testCompile (test-in-groovy) @ 
blueocean-parent ---
[INFO] No sources found to compile
[INFO] 
[INFO] --- maven-license-plugin:1.7:process (default) @ blueocean-parent ---
[INFO] Generated 
c:\JenkinsPlugs\blueocean-plugin\target\blueocean-parent\WEB-INF\licenses.xml
[INFO] 
[INFO] >>> findbugs-maven-plugin:3.0.3:check (findbugs) > :findbugs @ 
blueocean-parent >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.3:findbugs (findbugs) @ blueocean-parent 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.3:check (findbugs) < :findbugs @ 
blueocean-parent <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.3:check (findbugs) @ blueocean-parent ---
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
blueocean-parent ---
[INFO] Installing c:\JenkinsPlugs\blueocean-plugin\pom.xml to 
C:\Users\kazaky\.m2\repository\io\jenkins\blueocean\blueocean-parent\1.0-SNAPSHOT\blueocean-parent-1.0-SNAPSHOT.pom
[INFO] 
[INFO] 
[INFO] Building BlueOcean :: Commons API 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.6:clean (default-clean) @ blueocean-commons ---
[INFO] Deleting C:\JenkinsPlugs\blueocean-plugin\blueocean-commons\target
[INFO] 
[INFO] --- maven-hpi-plugin:1.117:validate (default-validate) @ 
blueocean-commons ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:display-info (display-info) @ 
blueocean-commons ---
[INFO] Maven Version: 3.3.9
[INFO] JDK Version: 1.8.0_91 normalized as: 1.8.0-91
[INFO] OS Info: Arch: amd64 Family: dos Name: windows 10 Version: 10.0
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (display-info) @ 
blueocean-commons ---
[INFO] 
[INFO]