Project

Profile

Help

Task #7911

repo generation issue

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

Status:
Closed
Priority:
High
Category:
mdbci features
Sprint/Milestone:
Start date:
19.01.2017
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

Mdbci fix: https://github.com/OSLL/mdbci/pull/335

Timogey's fix: https://github.com/mariadb-corporation/build-scripts-vagrant/pull/44/files

Testing: http://max-tst-01.mariadb.com:8089/view/All/job/run_test_snapshot/250/

Expectation: Check machine maxscale for that build. It's repo should have next link http://max-tst-01.mariadb.com/ci-repository//monitoring_of_particular_branch_set_in_maxscale-bsl-477/mariadb-maxscale//centos/7/$basearch


Description

markusjm [2:51 PM] 
there's something definitely wrong with the snapshot tests

[2:52] 
it uses a build from December 16th

[2:52] 
from commit d457f9cd03c120e5c8b0f07714e5232be5478bda

markusjm [3:00 PM] 
ah, I think this is the reason:
[ {
"product": "maxscale",
"version": "default",
"repo": "http://max-tst-01.mariadb.com/ci-repository//develop/mariadb-maxscale//centos/7/$basearch",
"repo_key": "http://maxscale-jenkins.mariadb.com/repository/release/mariadb-maxscale/Maxscale-GPG-KEY.public",
"platform": "centos",
"platform_version": "7"
}
]

[3:00] 
it always uses the develop repo

[3:00] 
I'll update the develop repo and see if it starts to use the newer one

[3:00] 
so the repo generation is somehow wrong

[3:01] 
it was last updated december 19th

History

#1 Updated by Mark Zaslavskiy almost 5 years ago

  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

#2 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#4 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

#5 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to New
  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

#6 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from New to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#7 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to Closed

Also available in: Atom PDF