Re: E-mails not reaching all receipients

2016-09-26 Thread rqui
Thanks for your reply, slide. So how could I explain that some users of a distribution group receive the emails, while others don't? On Monday, September 26, 2016 at 2:47:32 PM UTC-7, slide wrote: > > Nope, never had this issue. > > On Mon, Sep 26, 2016 at 1:20 PM rqui >

E-mails not reaching all receipients

2016-09-26 Thread rqui
Has anyone experienced any issue with using the email-ext plugin to send emails to a distribution list, with several subgroups, and it only reached some of the people on those lists? Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Jenkins Users

Re: How Do You Manage Growth?

2016-07-28 Thread rqui
That brings up another point...how does handling growth and implementing cloud (private or public) play a part as well? On Thursday, July 28, 2016 at 9:53:35 AM UTC-7, rqui wrote: > > I am seeking some advice/tips. Our group is experiencing fast growth and > changes and I am trying to

Re: How Do You Manage Growth?

2016-07-28 Thread rqui
> > Pretty sure we had a wiki page for that. If not, some day we should start > a section on that on the wiki or on Jenkins.io I guess. This question is > more and more often asked seems like. > > Le 28 juil. 2016 10:04 PM, "rqui" > a > écrit : > >> Al

Re: How Do You Manage Growth?

2016-07-28 Thread rqui
Also, how many users do you have in your Jenkins? On Thursday, July 28, 2016 at 11:31:42 AM UTC-7, Simona Avornicesei wrote: > > We have a single Jenkins master. > Depending on the needs of each team/project, they either have one or more > slaves/agents assigned exclusively for their jobs or the

Re: How Do You Manage Growth?

2016-07-28 Thread rqui
Do you only have the two teams? How do you manage the multiple nodes? Also how many users do you have using Jenkins? On Thursday, July 28, 2016 at 12:34:02 PM UTC-7, R Tyler Croy wrote: > > (replies inline) > > On Thu, 28 Jul 2016, rqui wrote: > > > I am seeking some advi

Re: How Do You Manage Growth?

2016-07-28 Thread rqui
How many teams use Jenkins and how many total nodes are used? On Thursday, July 28, 2016 at 11:31:42 AM UTC-7, Simona Avornicesei wrote: > > We have a single Jenkins master. > Depending on the needs of each team/project, they either have one or more > slaves/agents assigned exclusively for their

How Do You Manage Growth?

2016-07-28 Thread rqui
I am seeking some advice/tips. Our group is experiencing fast growth and changes and I am trying to architect a solution for managing it. We currently have a single master handling various types of jobs: ci, nightlies, releases, personal dev builds, etc. Using OSS, does anyone have experience

Re: LTS Release Snapshots

2015-10-13 Thread rqui
also Indra :) ) On Tuesday, October 13, 2015 at 12:19:11 PM UTC-7, Daniel Beck wrote: > > > On 13.10.2015, at 21:11, rqui > wrote: > > > How do I confirm that? > > The Jenkins log says which WAR file it's starting from, e.g.: > > > Running from: /va

Re: LTS Release Snapshots

2015-10-13 Thread rqui
How do I confirm that? On Tuesday, October 13, 2015 at 12:05:25 PM UTC-7, Daniel Beck wrote: > > > On 13.10.2015, at 21:02, rqui > wrote: > > > Thanks! I checked the /etc/init.d/jenkins script and it points to the > default location: /usr/lib/jenkins/jenkins.war >

Re: LTS Release Snapshots

2015-10-13 Thread rqui
appen) > *JENKINS_WAR="/usr/lib/jenkins/jenkins.war"* > > > From: > on behalf of rqui < > rhondaf...@gmail.com > > Reply-To: "jenkins...@googlegroups.com " < > jenkins...@googlegroups.com > > Date: Monday, October 12, 2015 at 4:40 PM > To: "

Re: LTS Release Snapshots

2015-10-12 Thread rqui
/jenkins.war by editing the > config files? > > On 13.10.2015, at 01:08, rqui > wrote: > > > I am using the yum repository to upgrade. I just installed the LTS > release: jenkins.noarch 0:1.609.3-1.1 > > > > > > On Monday, October 12, 2015 at 3:39:50

Re: Distribution Groups from Outlook

2015-10-12 Thread rqui
an "internet" email address (e.g. > your...@yourcompany.com ) then there's no reason for it not > to work as long as the distribution group is allowed to receive emails from > the "outside". > > Richard. > > On Tue, 13 Oct 2015 at 11:11 rqui > >

Re: LTS Release Snapshots

2015-10-12 Thread rqui
I am using the yum repository to upgrade. I just installed the LTS release: jenkins.noarch 0:1.609.3-1.1 On Monday, October 12, 2015 at 3:39:50 PM UTC-7, Daniel Beck wrote: > > How are you upgrading, and to which release? > > On 12.10.2015, at 23:44, rqui > wrot

Distribution Groups from Outlook

2015-10-12 Thread rqui
Hello, Does Jenkins (newer than v1.580) support the ability to use distribution groups from Outlook in the email-ext plugin? Thanks. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails fro

LTS Release Snapshots

2015-10-12 Thread rqui
Hello, Whenever I update to an LTS release, I get the "snapshot" version of it. How do I get the official GA version?? What is the difference between the "snapshot" and "non" snapshot? Thanks. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

Jenkins LTS updates

2015-04-22 Thread rqui
I am going to update our Jenkins version but on the website the latest LTS release is 1.596.2 and the rhel yum update version is 1.596.3. Any reason they are different? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this

Re: Issue with using ${BUILD_LOG_EXCERPT}

2015-04-17 Thread rqui
Nevermind. It's fixed. :-). I just made sure the regex was correct and there were no typos. Thanks. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-u

Re: Issue with using ${BUILD_LOG_EXCERPT}

2015-04-17 Thread rqui
Sorry. 1. The token doesn't get expanded in the actual email; it just displays the code as I have it in the job. 2. Sorry that's a typo on my part, its spelled correctly in my job. Do you really think its a "version" issue with the plugin and Jenkins? -- You received this message because you