Re: Any maintainer for the text-finder-plugin

[Oleg Nenashev]

>From what I see there is no maintainer around. Jesse (in Cc) was the last 
person who released it. Maybe he knows the context.

Could you please send me a list of plugins, where you created Pipeline 
support PRs? I will try to get some reviewers at least.

суббота, 5 ноября 2016 г., 21:26:56 UTC+3 пользователь Johnny Willemsen 
написал:
>
> Hi all,
>
> We switched last month to use the new pipeline support which turns out to 
> work as we hoped. 
>
> The only issue is that we used the text-finder-plugin which doesn't 
> support pipeline yet. I have made an attempt to fix some of the jenkins-ci 
> reported issues and added some support for pipeline, but being new in the 
> area of jenkins plugin development I could need some assistance in fixing 
> the last issue. Also it seems the plugin hasn't been maintained for some 
> time, anyone that is capable of checking my pull request and fixing the 
> last error so that this plugin will work  with pipeline? 
>
> FYI, the plugin is hosted at 
> https://github.com/jenkinsci/text-finder-plugin
>
> Best regards,
>
> Johnny
>

-- 
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/ace67bfe-5e21-490b-992c-10347bbca9f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git Parameter plugin ambiguous log messages

[Oleg Nenashev]

Have you created a JIRA ticket for it?
This mailing list is not a bugtracker && not all plugin maintainers read 
all messages.

среда, 16 ноября 2016 г., 23:44:19 UTC+3 пользователь Michael Giroux 
написал:
>
> The following log message would be a lot more informative if it provided 
> the job name so we could go adjust the configuration.
>
> Git Parameter Version 0.7.0
> Jenkins 2.19.2 LTS
> JDK 1.8
>
> Nov 16, 2016 8:36:01 PM 
> net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition 
> getBranch
> INFO: Specified branchFilter is not a valid regex. Setting to .*
>
>
>
>

-- 
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/900a3ba8-70c0-4797-b613-0ca80d5c3f02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to change the default value of Global Environment Variable through build job configuration at run time?

[Oleg Nenashev]

I think System Groovy script would be the best solution since they allow 
the access to Jenkins binary API. It should be used with care, but AFAIK it 
is the only way for such "exotic" use-cases 

See Groovy plugin and Scriptler plugin.

понедельник, 21 ноября 2016 г., 16:06:07 UTC+3 пользователь Kul Bhushan 
Srivastava написал:
>
> Can anybody suggest. How to do it?
>
> I tried to do it other way as well. I set a system environment variable 
> through 'Execute Windows Batch' build step. The variable got set 
> successfully. But it is not available in the next step unless I restart the 
> jenkins server.
>
> Please help.
>
> On Friday, 18 November 2016 23:16:36 UTC+5:30, Kul Bhushan Srivastava 
> wrote:
>>
>> How to change the default value of Global Environment Variable through 
>> build job configuration at run time?
>>
>

-- 
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/b5d31007-2b2d-4044-80ad-bd2aff75798e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Oleg Nenashev]

Hi Jacob,

On Wednesday we agreed with the proposed plan. Here is the meeting summary: 
http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-11-23-18.00.html

We agreed that I and Daniel will make the last attempt to reach out the 
original plugin maintainers with a final 2-week timeout. If we do not get a 
response, we will grant you the release permissions, no need in plugin 
renaming, etc.

I have granted you push permissions to 
https://github.com/jenkinsci/klocwork-plugin, hence you can start 
integrating changes there. I kindly recommend to consider using Pull 
requests and CCing jenkinsci/code-reviewers at the first steps (just to get 
some knowledge transfer). It is also recommended to update Jenkins core 
dependency to something newer and to use the new parent POM.

Best regards,
Oleg Nenashev 



среда, 23 ноября 2016 г., 11:19:27 UTC+3 пользователь Jacob Larfors написал:
>
> Many thanks for helping so much with this. The plan sounds good to me.
>
> My Jenkinsci account is: jlarfors
>
> Thanks again,
> Jacob
>
> On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:
>>
>> I have added the the topic to the agenda of the tomorrow's governance 
>> meeting: 
>> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting
>>
>> Jacob, could you please provide your Jenkinsci account?
>>
>> Thanks in advance,
>> Oleg
>>
>> вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev 
>> написал:
>>>
>>> In addition to this thread, I have tried to reach out Gregory directly 
>>> without success. Since he has left his original company as well as his 
>>> companion from citools org, it is a low chance we can proceed in the common 
>>> way.
>>>
>>> I had an f2f discussion with Jacob at Embedded Conference Scandinavia. 
>>> We discussed the current state and agreed on the following:
>>>
>>>1. Oleg will grant him an access to the klocwork repository within 
>>>the jenkinsci organization (an existing repo)
>>>2. Jacob will push the current changes in citools org and then 
>>>proceed with preparing the release in pull requests (he can use 
>>>jenkinsci/code-reviewers in order to get help with onboarding)
>>>3. Oleg will try to reach out Thales directly on behalf of the 
>>>Jenkins core team (in order to propose the ownership handover)
>>>4. If we do not get a response from Thales, we will submit a topic 
>>>to the Governance meeting with 2 options:
>>>   - Fork of a plugin with renaming/package name changes
>>>   - Just a takeover of the plugin by the Jenkins community (with 
>>>   temporary revokation of upload permissions for original maintainers 
>>> to 
>>>   avoid mess if they come back and do not notice this thread)
>>>   
>>> WDYT?
>>>
>>>
>>> Best regards,
>>>
>>> Oleg
>>>
>>>
>>> среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev 
>>> написал:

 Any revival of this plugin will be appreciated.

 Unfortunately, we cannot just fork the repository and start releasing 
 from it. It may be considered as a highjacking of the plugin. Plugin 
 maintainers commonly do not sign Jenkins CLA, hence we have no formal 
 permission to do so.

 I think we should fork the plugin to jenkinsci and start preparing it 
 to the release with patches (including stuff like CI, parent POM update, 
 etc.). If the maintainer does not respond, likely the only valid option 
 will be to rename plugin and to change packages to avoid data conflicts. 
 But it will require much work to implement the proper migration code.

 I've added Gregory Boissinot to Cc. Maybe he could suggest the proper 
 contact.

 BR, Oleg

 вторник, 15 ноября 2016 г., 14:13:29 UTC+1 пользователь Jacob Larfors 
 написал:
>
> Ok I tried contacting the other maintainer/user at cittools and his 
> email address for Thales does not work, so I suspect he has left Thales. 
> As 
> there has also been an outstanding pull request since July, and our 
> attempts to contact the people at cittools has failed, I would assume 
> this 
> repository is no longer taken care of...
>
> What options do we have? Can we make the jenkinsci repository the 
> "main" one and we will get our commits there? There arent really any 
> valid 
> PRs/FRs in Jira, and the few that are we could look to transfer or fix, 
> as 
> we quite actively work on this plugin and have been shipping hpi files 
> for 
> the past few years to avoid this mess and bottleneck of waiting for 
> cittools.
>
> Thanks for the help.
>
> Jacob
>
> On Tuesday, 15 November 2016 14:59:06 UTC+2, Jacob Larfors wrote:
>>
>> Hi Daniel, appreciate the quick feedback and thanks for the info - 
>> that answered another question I had about why the jenkinsci repo even 
>> existed.

Re: i've to create Jenkins Page that would check the server status by SOAP UI and if server is accessible then green status would return and if server not accessible then red status updated in desire

[Mark Waite]

It is rather uncommon to use Jenkins as a service health monitor, but you
might perform each of your checks as a JUnit test, write the results as a
JUnit file, then show the results as a JUnit test.  If a service is
unavailable, the JUnit results will show as a test failure.

If that's not a comfortable technique, you might consider creating a
multi-configuration job with one of the axes of the configurations being
the names of the servers you're checking.  A failure of one of those jobs
would be your indication that the service is not responding.

Mark Waite

On Fri, Nov 25, 2016 at 2:53 AM Gaganpreet Singh <
mail.2.gaganpr...@gmail.com> wrote:

> i've to create Jenkins Page that would check the server status by SOAP UI
> and if server is accessible then green status would return and if server
> not accessible then red status updated in desire column.
>
> *problem description*
>
> 1) We have 10 server on which latest build installed on daily basics, In
> Jenkins we wants to create a page which contains all 10 server and there
> corresponding status whether they are accessible or not (this will be
> checked by SOAPUI Script which we have,  if server is accessible then green
> status would return and if server not accessible then red status updated in
> desire column.)
>
>
> Question
>
> Pls suggest which Plugin we can use for the same?
>
> --
> 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/e1abb6f9-ea01-41f3-85ee-a1443b05bb10%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/CAO49JtEHMDsz70HWGWD2TnRjR9CkZpwOgQoNhi030Ls8oEivjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

i've to create Jenkins Page that would check the server status by SOAP UI and if server is accessible then green status would return and if server not accessible then red status updated in desire colu

[Gaganpreet Singh]

i've to create Jenkins Page that would check the server status by SOAP UI 
and if server is accessible then green status would return and if server 
not accessible then red status updated in desire column.

*problem description* 

1) We have 10 server on which latest build installed on daily basics, In 
Jenkins we wants to create a page which contains all 10 server and there 
corresponding status whether they are accessible or not (this will be 
checked by SOAPUI Script which we have,  if server is accessible then green 
status would return and if server not accessible then red status updated in 
desire column.)  


Question 

Pls suggest which Plugin we can use for the same?

-- 
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/e1abb6f9-ea01-41f3-85ee-a1443b05bb10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Develop a custom step that would make pipeline wait for a webhook

[Julien HENRY]

Hi guys,

We would like to implement a feature in the SonarQube plugin that would 
make the pipeline wait for some external/asynchronous processing to be 
completed (SonarQube analysis). In addition we would like to get some data 
(JSON payload) from this external process. Something like:

def analysisResult;
withSonarQubeEnv('mySonar') {
sh 'mvn sonar:sonar' // Submit asynchronous analysis
analysisResult = waitForSonarQubeAnalysis 
}
if (analysisResult.isSuccess) {
  promote()
} else {
  notifyKO(analysisResult)
}


I found this ticket https://issues.jenkins-ci.org/browse/JENKINS-27127 that 
is really close to what we need. Is there any progress on that topic? 
Waiting for this generic step, do you think it would be possible to 
implement the feature with a custom step?

Thanks

Julien

-- 
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/4f120390-f613-4ec9-9acd-303a7c9d3457%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.