Project

Profile

Help

Task #7975

Display link to build_info at build job email body

Added by Mark Zaslavskiy almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Timofey Turenko
Category:
jenkins_jobs
Sprint/Milestone:
Start date:
14.02.2017
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

https://github.com/mariadb-corporation/build-scripts-vagrant/pull/47/files

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/137/files

Testing: run http://maxscale-jenkins.mariadb.com:8090/job/7975_build/ that will execute build.sh, not fully only part with copy_repos.sh which will call generate_build_info_path.sh which will create files in workspace like build_info_env_var_* this file contains path to build info but without domain prefix, which will be added only in main section of job

Expectation: you will recieve mail with full link to build info (but you will not be able to watch that info because link is dummy link). Link shoud look like that: http://max-tst-01.mariadb.com/ci-repository//home/vagranttest/repository/develop/mariadb-maxscale//test4/dists/test2/main/binary-test3/build_info

Notice*: testing scripts used in job are on maxscale-jenkins server on path: ~/kaluzny/build-scripts-vagrant_7975/


Description

Initial info:
-- email от build - add link to build info (example http://max-tst-01.mariadb.com/ci-repository/2.1-feb6/mariadb-maxscale/centos/7/x86_64/build_info)
-- link generator https://github.com/mariadb-corporation/build-scripts-vagrant/blob/master/copy_repos/copy_repos.sh

What to do:
- refactor https://github.com/mariadb-corporation/build-scripts-vagrant/blob/master/copy_repos/copy_repos.sh
-- extract link path generation part to separated script generate_build_info_path.sh
-- call generate_build_info_path.sh from copy_repos.sh
- add link generated using generate_build_info_path.sh to build job email body

History

#1 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

https://github.com/mariadb-corporation/build-scripts-vagrant/pull/47/files

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/137/files

Testing: run http://maxscale-jenkins.mariadb.com:8090/job/7975_build/ that will execute build.sh, not fully only part with copy_repos.sh which will call generate_build_info_path.sh which will create files in workspace like build_info_env_var_* this file contains path to build info but without domain prefix, which will be added only in main section of job

Expectation: you will recieve mail with full link to build info (but you will not be able to watch that info because link is dummy link). Link shoud look like that: http://max-tst-01.mariadb.com/ci-repository//home/vagranttest/repository/develop/mariadb-maxscale//test4/dists/test2/main/binary-test3/build_info

#2 Updated by Alexander Kaluzhny almost 5 years ago

  • Test scenario updated (diff)

https://github.com/mariadb-corporation/build-scripts-vagrant/pull/47/files

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/137/files

Testing: run http://maxscale-jenkins.mariadb.com:8090/job/7975_build/ that will execute build.sh, not fully only part with copy_repos.sh which will call generate_build_info_path.sh which will create files in workspace like build_info_env_var_* this file contains path to build info but without domain prefix, which will be added only in main section of job

Expectation: you will recieve mail with full link to build info (but you will not be able to watch that info because link is dummy link). Link shoud look like that: http://max-tst-01.mariadb.com/ci-repository//home/vagranttest/repository/develop/mariadb-maxscale//test4/dists/test2/main/binary-test3/build_info

Notice*: testing scripts used in job are on maxscale-jenkins server on path: ~/kaluzny/build-scripts-vagrant_7975/

#3 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to Testing
  • Assignee changed from Mark Zaslavskiy to Timofey Turenko

#4 Updated by Timofey Turenko almost 5 years ago

  • Status changed from Testing to Closed

small issues fixed, closing

Also available in: Atom PDF