How do you all handle passwords when building your component dockers?
To build our apps and create our docker containers we have to specify
passwords, for example to our database. Today we put the passwords in our
build scripts, which are committed in git and exposed to the world. Our
Gary and community, please advise how best to integrate the new OParent POM.
On my first attempt Maven showed this error:
Could not find artifact org.onap.oparent:checkstyle:jar:1.0.0-SNAPSHOT in
apache.snapshots (http://repository.apache.org/snapshots)
I posted complete details about what
f there are, then modify them in your
> project definition
> 3) If there are not, then updating the job template to take a new
> variable is something that can be done, but then all projects that are
> using the template must be updated to pass a proper default so as to not
> break
Please advise how best to incorporate the oparent POM prepared by Gary Wu given
these differences among repositories. Currently that POM uses the ecomp- prefix
for server IDs in its distribution management block, but as you wrote, that
doesn't work for portal project.
> On Sep 7, 2017, at
Just want to mention that for our project (portal) the build time in the LF
Jenkins has dropped from 30 to 15 minutes, thank you LF for the recent
action(s) that resulted in this big speedup.
p.s. Can you find another 50%? :)
___
onap-discuss
Good day, definitely missing the Portal-apps VM! Please choose a Heat template
that deploys the just-released Amsterdam release of Portal, which is version
1.3.0, instead of the (much older) 1.1.0. Hope this helps.
> On Nov 22, 2017, at 8:52 AM, Muhammad Ali wrote:
>
This works for me (please note "https"):
git clone https://gerrit.onap.org/r/oom
> On Nov 22, 2017, at 5:32 AM, Kiruthiga R wrote:
>
> Hi All,
>
> As part of ONAP on Kubernetes installation, while trying to clone the oom
> repo using anonymous http method (git
The build process for Portal and Portal/SDK is done together, and automated in
the LF Jenkins system. The two parts must be obtained from two different Git
repositories ("portal" and "portal/sdk"). My best guess is that this build was
attempted with only the first repo checked out, and without
This is (or should be) already done, Marco merged the required change this
morning:
https://gerrit.onap.org/r/#/c/21299/
> On Oct 30, 2017, at 1:51 PM, Gary Wu wrote:
>
> Please see update from Chris Lott in https://jira.onap.org/browse/PORTAL-138:
> It seems that we
All I can offer is my experience, namely that the deploy step failed when my
POM used "ecomp-snapshots":
https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/portal-sdk-master-ecomp-sdk-merge-java/12/console.log.gz
And succeeded when my POM used "snapshots":
10 matches
Mail list logo