> -----Original Message-----
> From: dhinakar k [mailto:dhinakar.k@gmail.com]
> Sent: Monday, April 10, 2017 9:01 PM
> Thanks for your response.
> It seems the problem is due to the Jenkins port & service issue. I was have plain vanilla Jenkins running at 8080 port and wanted to
> setup Fuego at 8081. So temporarily stopped Jenkins service @8080. This caused the issue. Now I have swapped the ports so that I can
> go with defaults to make things easy for Fuego. So that issue is solved now.
Thanks for reporting Dhinakar.
I will add support for specifying a different port to the Dockerfile.
Daniel
>
> On Apr 10, 2017 7:23 AM, "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp <mailto:daniel.sangorrin@toshiba.co.jp > > wrote:
>
>
> > -----Original Message-----
> > From: fuego-bounces@lists.linuxfoundation.org <mailto:fuego-bounces@lists.linuxfoundation.org > [mailto:fuego-
> bounces@lists.linuxfoundation.org <mailto:fuego-bounces@lists.linuxfoundation.org > ] On Behalf Of dhinakar k
> > ---> Running in 9cc9272ed6a4
> > ---> 85db72cbfc81
> > Removing intermediate container 9cc9272ed6a4
> > Step 32 : RUN source /etc/default/jenkins && JAVA_ARGS="$JAVA_ARGS -Djenkins.install.runSetupWizard=false" && if
> [ -n
> > "$HTTP_PROXY" ]; then PROXYSERVER=$(echo $http_proxy | sed -E 's/^http://' | sed -E 's/\///g' | sed -E
> 's/(.*):(.*)/\1/') &&
> > PROXYPORT=$(echo $http_proxy | sed -E 's/^http://' | sed -E 's/\///g' | sed -E 's/(.*):(.*)/\2/') &&
> JAVA_ARGS="$JAVA_ARGS -
> > Dhttp.proxyHost="${PROXYSERVER}" -Dhttp.proxyPort="${PROXYPORT} " -Dhttps.proxyHost="${ PROXYSERVER}" -
> > Dhttps.proxyPort="${PROXYPORT}; fi && sed -i -e "s#^JAVA_ARGS.*#JAVA_ARGS\=\"$ {JAVA_ARGS}\"#g"
> /etc/default/jenkins;
> > ---> Running in 6721c884cf16
> > ---> 027eb9ad54a5
> > Removing intermediate container 6721c884cf16
> > Step 33 : RUN service jenkins start && sleep 30 && sudo -u jenkins java -jar /var/cache/jenkins/war/WEB-INF/jenkins-
> cli.jar -s
> > http://localhost:8080/fuego install-plugin description-setter && sudo -u jenkins java -jar /var/cache/jenkins/war/WEB-
> INF/jenkins-
> > cli.jar -s http://localhost:8080/fuego install-plugin pegdown-formatter
> > ---> Running in bfbc88626a6f
> > Starting Jenkins Continuous Integration Server: jenkins.
> > description-setter is neither a valid file, URL, nor a plugin artifact name in the update center
> > No update center data is retrieved yet from: http://updates.jenkins-ci.org/update-center.json <http://updates.jenkins-
> ci.org/update-center.json>
> > description-setter looks like a short plugin name. Did you mean ?null??
> >
> > ERROR: Error occurred, see previous output.
> > The command '/bin/sh -c service jenkins start && sleep 30 && sudo -u jenkins java -jar /var/cache/jenkins/war/WEB-
> INF/jenkins-
> > cli.jar -s http://localhost:8080/fuego install-plugin description-setter && sudo -u jenkins java -jar
> /var/cache/jenkins/war/WEB-
> > INF/jenkins-cli.jar -s http://localhost:8080/fuego install-plugin pegdown-formatter' returned a non-zero code: 5
> > [sudo] password for dhinakar:
> >
> >
> >
> > Any clue what is the issue?
>
> It may be a problem with your environment/company network(?).
> You could install it without plugins first, and then install the plugins by hand from the Jenkins interface.
>
> Thanks,
> Daniel
>
>
>
>
>