Size: a a a

2020 July 30

P

Pavel in jenkins_ru
FROM python:3.8-slim-buster

LABEL version="0.2"

LABEL release-date="2020-07-30"

ARG ALLURE_REPO=https://dl.bintray.com/qameta/maven/io/qameta/allure/allure-commandline
ARG ALLURE_RELEASE=2.13.5

ENV ALLURE_HOME=/allure-$ALLURE_RELEASE
ENV PATH=$PATH:$ALLURE_HOME/bin

# Update packages  and install dependencies
RUN apt-get update -y
RUN apt-get install -fy unzip curl
RUN pip install --upgrade pip
RUN curl ${ALLURE_REPO}/${ALLURE_RELEASE}/allure-commandline-${ALLURE_RELEASE}.zip -L -o /tmp/allure-commandline.zip && unzip -q /tmp/allure-commandline.zip -d / && chmod -R +x /allure-$ALLURE_RELEASE/bin
RUN echo $(ls -1 ${ALLURE_HOME})
RUN echo ${PATH}
#RUN pip install pytest
источник

I

Ilgiz in jenkins_ru
Pavel
FROM python:3.8-slim-buster

LABEL version="0.2"

LABEL release-date="2020-07-30"

ARG ALLURE_REPO=https://dl.bintray.com/qameta/maven/io/qameta/allure/allure-commandline
ARG ALLURE_RELEASE=2.13.5

ENV ALLURE_HOME=/allure-$ALLURE_RELEASE
ENV PATH=$PATH:$ALLURE_HOME/bin

# Update packages  and install dependencies
RUN apt-get update -y
RUN apt-get install -fy unzip curl
RUN pip install --upgrade pip
RUN curl ${ALLURE_REPO}/${ALLURE_RELEASE}/allure-commandline-${ALLURE_RELEASE}.zip -L -o /tmp/allure-commandline.zip && unzip -q /tmp/allure-commandline.zip -d / && chmod -R +x /allure-$ALLURE_RELEASE/bin
RUN echo $(ls -1 ${ALLURE_HOME})
RUN echo ${PATH}
#RUN pip install pytest
Чёто херня. Короче, сделай так, чтобы аллюр-кли запускался у тебя в докере без указания пути. Мне лень и не хочется писать как это сделать
источник

P

Pavel in jenkins_ru
источник

I

Ilgiz in jenkins_ru
И файл должен называться allure, судя по ошибке сверху
источник

P

Pavel in jenkins_ru
``````
источник

P

Pavel in jenkins_ru
---> Running in becf74760ab1

ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

The command '/bin/sh -c allure --help' returned a non-zero code: 1
источник

P

Pavel in jenkins_ru
хехе
источник
2020 July 31

P

Pavel in jenkins_ru
привет, получилось запустить allure в docker, теперь осталось решить с Jenkins
[Check_Errors] $ docker exec --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** 4ee0df6ccd74310294c8ccd1121ddd9f989c474448b723ddef0053dbc8957747 /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure generate /var/lib/jenkins/workspace/Check_Errors/allure-reports -c -o /var/lib/jenkins/workspace/Check_Errors/allure-report
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"/var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure\": stat /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure: no such file or directory": unknown
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
$ docker stop --time=1 4ee0df6ccd74310294c8ccd1121ddd9f989c474448b723ddef0053dbc8957747
$ docker rm -f 4ee0df6ccd74310294c8ccd1121ddd9f989c474448b723ddef0053dbc8957747
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ru.yandex.qatools.allure.jenkins.exception.AllurePluginException: Can not generate Allure Report, exit code: 126
 at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.generateReport(AllureReportPublisher.java:314)
 at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.perform(AllureReportPublisher.java:231)
 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)
 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)
 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
источник

E

Elenhil in jenkins_ru
Pavel
привет, получилось запустить allure в docker, теперь осталось решить с Jenkins
[Check_Errors] $ docker exec --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** 4ee0df6ccd74310294c8ccd1121ddd9f989c474448b723ddef0053dbc8957747 /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure generate /var/lib/jenkins/workspace/Check_Errors/allure-reports -c -o /var/lib/jenkins/workspace/Check_Errors/allure-report
OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "exec: \"/var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure\": stat /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure: no such file or directory": unknown
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
$ docker stop --time=1 4ee0df6ccd74310294c8ccd1121ddd9f989c474448b723ddef0053dbc8957747
$ docker rm -f 4ee0df6ccd74310294c8ccd1121ddd9f989c474448b723ddef0053dbc8957747
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ru.yandex.qatools.allure.jenkins.exception.AllurePluginException: Can not generate Allure Report, exit code: 126
 at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.generateReport(AllureReportPublisher.java:314)
 at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.perform(AllureReportPublisher.java:231)
 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)
 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)
 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
/var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure
источник

E

Elenhil in jenkins_ru
видимо не получилось
источник

E

Elenhil in jenkins_ru
раз файла нет такого
источник

P

Pavel in jenkins_ru
через shell script allure работает
источник

E

Elenhil in jenkins_ru
Pavel
через shell script allure работает
идентичный запуск?
источник

E

Elenhil in jenkins_ru
/var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure generate /var/lib/jenkins/workspace/Check_Errors/allure-reports -c -o /var/lib/jenkins/workspace/Check_Errors/allure-report
источник

P

Pavel in jenkins_ru
у меня тесты в docker
источник

E

Elenhil in jenkins_ru
и что?
источник

E

Elenhil in jenkins_ru
Запусти докер контейнер с ентрипоинт sleep infintiy
источник

E

Elenhil in jenkins_ru
и сделай там руками
источник

E

Elenhil in jenkins_ru
и увидишь проблему
источник

E

Elenhil in jenkins_ru
дженкинс тут ни причем, он тебе же написал - нет файла
источник