[jira] [Commented] (BUILDS-85) Could not generate DH keypair / peer not authenticated
[ https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706681#comment-14706681 ] Martin Grigorov commented on BUILDS-85: --- I've tried but it seems BuildBot has problems. My change is waiting for more than 5 hours in the build queue: (Aug 21 07:17:47, waiting 5 hrs, 2 mins, 37 secs) 30935617d926... (Martin Tzvetanov Grigorov ) See https://ci.apache.org/builders/wicket-branch-6.x > Could not generate DH keypair / peer not authenticated > --- > > Key: BUILDS-85 > URL: https://issues.apache.org/jira/browse/BUILDS-85 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Andreas Lehmkühler >Assignee: Tony Stevenson > Attachments: SSLPoke.java > > > We're getting this since june 10th: > [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ pdfbox-parent --- > Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/1.8.10-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.apache.pdfbox:pdfbox-parent:1.8.10-SNAPSHOT/maven-metadata.xml from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): Error > transferring file: java.lang.RuntimeException: Could not generate DH keypair > and this: > [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ pdfbox-parent > --- > Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/2.0.0-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.apache.pdfbox:pdfbox-parent:2.0.0-SNAPSHOT/maven-metadata.xml from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): peer not > authenticated > The issue seems to be jdk related as only those builds using java 1.6.0_37 > (unlimited security) are failing. I've reconfigured the trunk build to use > java 7 and everything works fine, as well as our jdk7 based branch build. > Any ideas? Maybe a plugin update which doesn't work with java6? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: FYI - disabled timer triggers across the board on builds.apache.org
I’ve noticed that this change has pretty much disabled Hadoop world spefici precommit [1] hook as this job is running every 10 minutes and fetching updates from JIRA, rather then following any repository. I’ve put back the “run every 10 minutes”. This job is usually done in less then 30 seconds, so I’m assuming that it won’t be a problem :) Jarcec Links: 1: https://builds.apache.org/job/PreCommit-Admin > On Aug 20, 2015, at 10:32 AM, Andrew Bayer wrote: > > I noticed a lot of jobs that were running every day regardless of whether > anything changed and eating up a lot of executors, so I bulk-removed all of > them, changing those jobs to poll for changes hourly instead. If your > project has one or two jobs that you need to run daily whether there are > code changes or not, you can re-enable the timer, but please do not do that > for more than a couple jobs, and please do not do it for jobs that take > longer than half an hour. > > A.
What is the process of reporting dead slaves
Looking at Jenkins queue - there is 132 queued jobs and only 4 working executors :) All the others are marked as “DEAD”. I’m wondering what is the process of reporting that? Should I create BUILDS or INFRA JIRA, or just send email to this group or something completely else? Jarcec
Re: FYI - disabled timer triggers across the board on builds.apache.org
Oops, sorry about that! On Aug 21, 2015 12:02, "Jarek Jarcec Cecho" wrote: > I’ve noticed that this change has pretty much disabled Hadoop world > spefici precommit [1] hook as this job is running every 10 minutes and > fetching updates from JIRA, rather then following any repository. I’ve put > back the “run every 10 minutes”. This job is usually done in less then 30 > seconds, so I’m assuming that it won’t be a problem :) > > Jarcec > > Links: > 1: https://builds.apache.org/job/PreCommit-Admin > > > On Aug 20, 2015, at 10:32 AM, Andrew Bayer > wrote: > > > > I noticed a lot of jobs that were running every day regardless of whether > > anything changed and eating up a lot of executors, so I bulk-removed all > of > > them, changing those jobs to poll for changes hourly instead. If your > > project has one or two jobs that you need to run daily whether there are > > code changes or not, you can re-enable the timer, but please do not do > that > > for more than a couple jobs, and please do not do it for jobs that take > > longer than half an hour. > > > > A. > >
Re: What is the process of reporting dead slaves
I'll take a look in 30 minutes or so. On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: > Looking at Jenkins queue - there is 132 queued jobs and only 4 working > executors :) All the others are marked as “DEAD”. > > I’m wondering what is the process of reporting that? Should I create > BUILDS or INFRA JIRA, or just send email to this group or something > completely else? > > Jarcec
Re: FYI - disabled timer triggers across the board on builds.apache.org
No worries, I completely get why we made this change across the board. I actually feel bad that I didn’t realize the consequences yesterday when I read the email and had to spend good half an hour figuring it out :) Jarcec > On Aug 21, 2015, at 9:17 AM, Andrew Bayer wrote: > > Oops, sorry about that! > On Aug 21, 2015 12:02, "Jarek Jarcec Cecho" wrote: > >> I’ve noticed that this change has pretty much disabled Hadoop world >> spefici precommit [1] hook as this job is running every 10 minutes and >> fetching updates from JIRA, rather then following any repository. I’ve put >> back the “run every 10 minutes”. This job is usually done in less then 30 >> seconds, so I’m assuming that it won’t be a problem :) >> >> Jarcec >> >> Links: >> 1: https://builds.apache.org/job/PreCommit-Admin >> >>> On Aug 20, 2015, at 10:32 AM, Andrew Bayer >> wrote: >>> >>> I noticed a lot of jobs that were running every day regardless of whether >>> anything changed and eating up a lot of executors, so I bulk-removed all >> of >>> them, changing those jobs to poll for changes hourly instead. If your >>> project has one or two jobs that you need to run daily whether there are >>> code changes or not, you can re-enable the timer, but please do not do >> that >>> for more than a couple jobs, and please do not do it for jobs that take >>> longer than half an hour. >>> >>> A. >> >>
Re: What is the process of reporting dead slaves
We ran out of disk space on builds.a.o - I'm compressing the 487gb (!!!) of logs and will work with the rest of Infra to make sure that's done automatically. A. On Fri, Aug 21, 2015 at 12:18 PM, Andrew Bayer wrote: > I'll take a look in 30 minutes or so. > On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: > >> Looking at Jenkins queue - there is 132 queued jobs and only 4 working >> executors :) All the others are marked as “DEAD”. >> >> I’m wondering what is the process of reporting that? Should I create >> BUILDS or INFRA JIRA, or just send email to this group or something >> completely else? >> >> Jarcec > >
Re: FYI - disabled timer triggers across the board on builds.apache.org
Polling would be fine for us, even @daily. But it seems the polling doesn't work, see [1]. There is only the icon but the "Subversion Polling Log" label is missing. When clicking on the icon it shown an error. For another job [2] I went into "Configure" and just saved without any further modification, then the polling seems to work. Kind Regards, Stefan [1] https://builds.apache.org/view/A-D/view/Directory/job/dir-studio/ [2] https://builds.apache.org/view/A-D/view/Directory/job/dir-shared-ubuntu-deploy/ On 08/20/2015 07:32 PM, Andrew Bayer wrote: > I noticed a lot of jobs that were running every day regardless of whether > anything changed and eating up a lot of executors, so I bulk-removed all of > them, changing those jobs to poll for changes hourly instead. If your > project has one or two jobs that you need to run daily whether there are > code changes or not, you can re-enable the timer, but please do not do that > for more than a couple jobs, and please do not do it for jobs that take > longer than half an hour. > > A. >
Re: What is the process of reporting dead slaves
Thanks Andrew! Just to give you heads up - it just seems that the build slaves went out of disk space as I see this exception: java.io.IOException: No space left on device (probably some rogue job or something) Jarcec > On Aug 21, 2015, at 9:18 AM, Andrew Bayer wrote: > > I'll take a look in 30 minutes or so. > On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: > >> Looking at Jenkins queue - there is 132 queued jobs and only 4 working >> executors :) All the others are marked as “DEAD”. >> >> I’m wondering what is the process of reporting that? Should I create >> BUILDS or INFRA JIRA, or just send email to this group or something >> completely else? >> >> Jarcec
Re: What is the process of reporting dead slaves
It's not the slaves, it's the master itself. A. On Fri, Aug 21, 2015 at 12:32 PM, Jarek Jarcec Cecho wrote: > Thanks Andrew! > > Just to give you heads up - it just seems that the build slaves went out > of disk space as I see this exception: > > java.io.IOException: No space left on device > > (probably some rogue job or something) > > Jarcec > > > On Aug 21, 2015, at 9:18 AM, Andrew Bayer > wrote: > > > > I'll take a look in 30 minutes or so. > > On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: > > > >> Looking at Jenkins queue - there is 132 queued jobs and only 4 working > >> executors :) All the others are marked as “DEAD”. > >> > >> I’m wondering what is the process of reporting that? Should I create > >> BUILDS or INFRA JIRA, or just send email to this group or something > >> completely else? > >> > >> Jarcec > >
Re: FYI - disabled timer triggers across the board on builds.apache.org
Hmm, I'll take a look - I'm restarting builds.a.o right now to deal with the out of space issue. A. On Fri, Aug 21, 2015 at 12:31 PM, Stefan Seelmann wrote: > Polling would be fine for us, even @daily. > > But it seems the polling doesn't work, see [1]. There is only the icon > but the "Subversion Polling Log" label is missing. When clicking on the > icon it shown an error. > > For another job [2] I went into "Configure" and just saved without any > further modification, then the polling seems to work. > > Kind Regards, > Stefan > > [1] https://builds.apache.org/view/A-D/view/Directory/job/dir-studio/ > > [2] > > https://builds.apache.org/view/A-D/view/Directory/job/dir-shared-ubuntu-deploy/ > > On 08/20/2015 07:32 PM, Andrew Bayer wrote: > > I noticed a lot of jobs that were running every day regardless of whether > > anything changed and eating up a lot of executors, so I bulk-removed all > of > > them, changing those jobs to poll for changes hourly instead. If your > > project has one or two jobs that you need to run daily whether there are > > code changes or not, you can re-enable the timer, but please do not do > that > > for more than a couple jobs, and please do not do it for jobs that take > > longer than half an hour. > > > > A. > > > > >
Re: FYI - disabled timer triggers across the board on builds.apache.org
Ok, I think the restart seems to have cleared up the polling on jobs - sorry, I'll figure out a better way to handle this sort of thing in the future. A. On Fri, Aug 21, 2015 at 12:31 PM, Stefan Seelmann wrote: > Polling would be fine for us, even @daily. > > But it seems the polling doesn't work, see [1]. There is only the icon > but the "Subversion Polling Log" label is missing. When clicking on the > icon it shown an error. > > For another job [2] I went into "Configure" and just saved without any > further modification, then the polling seems to work. > > Kind Regards, > Stefan > > [1] https://builds.apache.org/view/A-D/view/Directory/job/dir-studio/ > > [2] > > https://builds.apache.org/view/A-D/view/Directory/job/dir-shared-ubuntu-deploy/ > > On 08/20/2015 07:32 PM, Andrew Bayer wrote: > > I noticed a lot of jobs that were running every day regardless of whether > > anything changed and eating up a lot of executors, so I bulk-removed all > of > > them, changing those jobs to poll for changes hourly instead. If your > > project has one or two jobs that you need to run daily whether there are > > code changes or not, you can re-enable the timer, but please do not do > that > > for more than a couple jobs, and please do not do it for jobs that take > > longer than half an hour. > > > > A. > > > > >
Re: What is the process of reporting dead slaves
Everything's lively again now - I'll make sure we've got disk space monitoring in place again. A. On Fri, Aug 21, 2015 at 12:33 PM, Andrew Bayer wrote: > It's not the slaves, it's the master itself. > > A. > > On Fri, Aug 21, 2015 at 12:32 PM, Jarek Jarcec Cecho > wrote: > >> Thanks Andrew! >> >> Just to give you heads up - it just seems that the build slaves went out >> of disk space as I see this exception: >> >> java.io.IOException: No space left on device >> >> (probably some rogue job or something) >> >> Jarcec >> >> > On Aug 21, 2015, at 9:18 AM, Andrew Bayer >> wrote: >> > >> > I'll take a look in 30 minutes or so. >> > On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: >> > >> >> Looking at Jenkins queue - there is 132 queued jobs and only 4 working >> >> executors :) All the others are marked as “DEAD”. >> >> >> >> I’m wondering what is the process of reporting that? Should I create >> >> BUILDS or INFRA JIRA, or just send email to this group or something >> >> completely else? >> >> >> >> Jarcec >> >> >
Re: What is the process of reporting dead slaves
Got it, it looks much better now - thank you! Jarcec > On Aug 21, 2015, at 9:33 AM, Andrew Bayer wrote: > > It's not the slaves, it's the master itself. > > A. > > On Fri, Aug 21, 2015 at 12:32 PM, Jarek Jarcec Cecho > wrote: > >> Thanks Andrew! >> >> Just to give you heads up - it just seems that the build slaves went out >> of disk space as I see this exception: >> >> java.io.IOException: No space left on device >> >> (probably some rogue job or something) >> >> Jarcec >> >>> On Aug 21, 2015, at 9:18 AM, Andrew Bayer >> wrote: >>> >>> I'll take a look in 30 minutes or so. >>> On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: >>> Looking at Jenkins queue - there is 132 queued jobs and only 4 working executors :) All the others are marked as “DEAD”. I’m wondering what is the process of reporting that? Should I create BUILDS or INFRA JIRA, or just send email to this group or something completely else? Jarcec >> >>
Re: What is the process of reporting dead slaves
FWIW, https://issues.apache.org/jira/browse/INFRA-10171 will help us catch this earlier, and https://issues.apache.org/jira/browse/INFRA-10172 will help keep it from happening in the first place. I'm also looking to see what jobs are using the most disk space to try to trim their usage down. On Fri, Aug 21, 2015 at 12:56 PM, Jarek Jarcec Cecho wrote: > Got it, it looks much better now - thank you! > > Jarcec > > > On Aug 21, 2015, at 9:33 AM, Andrew Bayer > wrote: > > > > It's not the slaves, it's the master itself. > > > > A. > > > > On Fri, Aug 21, 2015 at 12:32 PM, Jarek Jarcec Cecho > > wrote: > > > >> Thanks Andrew! > >> > >> Just to give you heads up - it just seems that the build slaves went out > >> of disk space as I see this exception: > >> > >> java.io.IOException: No space left on device > >> > >> (probably some rogue job or something) > >> > >> Jarcec > >> > >>> On Aug 21, 2015, at 9:18 AM, Andrew Bayer > >> wrote: > >>> > >>> I'll take a look in 30 minutes or so. > >>> On Aug 21, 2015 12:05, "Jarek Jarcec Cecho" wrote: > >>> > Looking at Jenkins queue - there is 132 queued jobs and only 4 working > executors :) All the others are marked as “DEAD”. > > I’m wondering what is the process of reporting that? Should I create > BUILDS or INFRA JIRA, or just send email to this group or something > completely else? > > Jarcec > >> > >> > >
Re: FYI - disabled timer triggers across the board on builds.apache.org
On 08/21/2015 06:50 PM, Andrew Bayer wrote: > Ok, I think the restart seems to have cleared up the polling on jobs - > sorry, I'll figure out a better way to handle this sort of thing in the > future. Thanks Andrew. I changed all Directory jobs to poll @daily only, should be sufficient for our needs.
[jira] [Commented] (BUILDS-85) Could not generate DH keypair / peer not authenticated
[ https://issues.apache.org/jira/browse/BUILDS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707295#comment-14707295 ] Martin Grigorov commented on BUILDS-85: --- Everything is green again: https://ci.apache.org/builders/wicket-branch-6.x/builds/32 ! Thanks a lot! > Could not generate DH keypair / peer not authenticated > --- > > Key: BUILDS-85 > URL: https://issues.apache.org/jira/browse/BUILDS-85 > Project: Infra Build Platform > Issue Type: Bug > Components: Jenkins >Reporter: Andreas Lehmkühler >Assignee: Tony Stevenson > Attachments: SSLPoke.java > > > We're getting this since june 10th: > [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ pdfbox-parent --- > Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/1.8.10-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.apache.pdfbox:pdfbox-parent:1.8.10-SNAPSHOT/maven-metadata.xml from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): Error > transferring file: java.lang.RuntimeException: Could not generate DH keypair > and this: > [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ pdfbox-parent > --- > Downloading:https://repository.apache.org/content/repositories/snapshots/org/apache/pdfbox/pdfbox-parent/2.0.0-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.apache.pdfbox:pdfbox-parent:2.0.0-SNAPSHOT/maven-metadata.xml from/to > apache.snapshots.https > (https://repository.apache.org/content/repositories/snapshots): peer not > authenticated > The issue seems to be jdk related as only those builds using java 1.6.0_37 > (unlimited security) are failing. I've reconfigured the trunk build to use > java 7 and everything works fine, as well as our jdk7 based branch build. > Any ideas? Maybe a plugin update which doesn't work with java6? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: There was no nightly build yesterday?
Hi, We need to have the nightly build reenabled for Apache Geode incubating. Who do we need to speak with to make this happen? Thanks, Kirk On Fri, Aug 21, 2015 at 11:06 AM, Kirk Lund wrote: > Hi Andrew, > > Please reenable our nightly build. It's about a 6 hour run and we don't > want that triggered hourly. It was set to nightly because we are checking > in changes every day but didn't want the build system to attempt to run all > of those nightly tests every hour. > > Thanks, > Kirk > > > On Fri, Aug 21, 2015 at 10:33 AM, Andrew Bayer > wrote: > > > See the email I sent to builds@. We disabled all timer triggers because > a > > lot of jobs were set to run daily even if nothing changed, using up a lot > > of resources for no good reason. If you've got a couple jobs that you > want > > running daily whether there are changes or not and they don't take an > > excessive amount of time, you can switch back to daily. > > > > A. > > > > On Fri, Aug 21, 2015 at 1:31 PM, Mark Bretl wrote: > > > > > Looks as though user abayer changed the build nightly to poll SCM > > 'hourly'. > > > > > > Andrew, can you explain why you made the configuration change to the > > Geode > > > Nightly build job? > > > > > > Best Regards, > > > > > > --Mark > > > > > > On Fri, Aug 21, 2015 at 9:58 AM, Ashvin A wrote: > > > > > >> Hi, > > >> > > >> I was expecting to see build 191 results today morning. It seems the > > >> nightly build did not happen or is stuck. There is no build mail or > > build > > >> activity on https://builds.apache.org/job/Geode-nightly/. > > >> > > >> Anyone knows more about it? > > >> > > >> Thank you, > > >> Ashvin > > >> > > > > > > > > > > > > -- > > > Mark Bretl > > > Software Build Engineer > > > Pivotal > > > 503-533-3869 > > > www.pivotal.io > > > > > >
Re: There was no nightly build yesterday?
I will re-enable the nightly schedule. --Mark On Fri, Aug 21, 2015 at 1:11 PM, Kirk Lund wrote: > Hi, > > We need to have the nightly build reenabled for Apache Geode incubating. > Who do we need to speak with to make this happen? > > Thanks, > Kirk > > On Fri, Aug 21, 2015 at 11:06 AM, Kirk Lund wrote: > >> Hi Andrew, >> >> Please reenable our nightly build. It's about a 6 hour run and we don't >> want that triggered hourly. It was set to nightly because we are checking >> in changes every day but didn't want the build system to attempt to run >> all >> of those nightly tests every hour. >> >> Thanks, >> Kirk >> >> >> On Fri, Aug 21, 2015 at 10:33 AM, Andrew Bayer >> wrote: >> >> > See the email I sent to builds@. We disabled all timer triggers >> because a >> > lot of jobs were set to run daily even if nothing changed, using up a >> lot >> > of resources for no good reason. If you've got a couple jobs that you >> want >> > running daily whether there are changes or not and they don't take an >> > excessive amount of time, you can switch back to daily. >> > >> > A. >> > >> > On Fri, Aug 21, 2015 at 1:31 PM, Mark Bretl wrote: >> > >> > > Looks as though user abayer changed the build nightly to poll SCM >> > 'hourly'. >> > > >> > > Andrew, can you explain why you made the configuration change to the >> > Geode >> > > Nightly build job? >> > > >> > > Best Regards, >> > > >> > > --Mark >> > > >> > > On Fri, Aug 21, 2015 at 9:58 AM, Ashvin A wrote: >> > > >> > >> Hi, >> > >> >> > >> I was expecting to see build 191 results today morning. It seems the >> > >> nightly build did not happen or is stuck. There is no build mail or >> > build >> > >> activity on https://builds.apache.org/job/Geode-nightly/. >> > >> >> > >> Anyone knows more about it? >> > >> >> > >> Thank you, >> > >> Ashvin >> > >> >> > > >> > > >> > > >> > > -- >> > > Mark Bretl >> > > Software Build Engineer >> > > Pivotal >> > > 503-533-3869 >> > > www.pivotal.io >> > > >> > >> > > -- Mark Bretl Software Build Engineer Pivotal 503-533-3869 www.pivotal.io
Re: There was no nightly build yesterday?
Thanks Mark! On Fri, Aug 21, 2015 at 1:13 PM, Mark Bretl wrote: > I will re-enable the nightly schedule. > > --Mark > > On Fri, Aug 21, 2015 at 1:11 PM, Kirk Lund wrote: > > > Hi, > > > > We need to have the nightly build reenabled for Apache Geode incubating. > > Who do we need to speak with to make this happen? > > > > Thanks, > > Kirk > > > > On Fri, Aug 21, 2015 at 11:06 AM, Kirk Lund wrote: > > > >> Hi Andrew, > >> > >> Please reenable our nightly build. It's about a 6 hour run and we don't > >> want that triggered hourly. It was set to nightly because we are > checking > >> in changes every day but didn't want the build system to attempt to run > >> all > >> of those nightly tests every hour. > >> > >> Thanks, > >> Kirk > >> > >> > >> On Fri, Aug 21, 2015 at 10:33 AM, Andrew Bayer > >> wrote: > >> > >> > See the email I sent to builds@. We disabled all timer triggers > >> because a > >> > lot of jobs were set to run daily even if nothing changed, using up a > >> lot > >> > of resources for no good reason. If you've got a couple jobs that you > >> want > >> > running daily whether there are changes or not and they don't take an > >> > excessive amount of time, you can switch back to daily. > >> > > >> > A. > >> > > >> > On Fri, Aug 21, 2015 at 1:31 PM, Mark Bretl > wrote: > >> > > >> > > Looks as though user abayer changed the build nightly to poll SCM > >> > 'hourly'. > >> > > > >> > > Andrew, can you explain why you made the configuration change to the > >> > Geode > >> > > Nightly build job? > >> > > > >> > > Best Regards, > >> > > > >> > > --Mark > >> > > > >> > > On Fri, Aug 21, 2015 at 9:58 AM, Ashvin A > wrote: > >> > > > >> > >> Hi, > >> > >> > >> > >> I was expecting to see build 191 results today morning. It seems > the > >> > >> nightly build did not happen or is stuck. There is no build mail or > >> > build > >> > >> activity on https://builds.apache.org/job/Geode-nightly/. > >> > >> > >> > >> Anyone knows more about it? > >> > >> > >> > >> Thank you, > >> > >> Ashvin > >> > >> > >> > > > >> > > > >> > > > >> > > -- > >> > > Mark Bretl > >> > > Software Build Engineer > >> > > Pivotal > >> > > 503-533-3869 > >> > > www.pivotal.io > >> > > > >> > > >> > > > > > > > -- > Mark Bretl > Software Build Engineer > Pivotal > 503-533-3869 > www.pivotal.io >
