You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This bug is highly related to another issue mentioned here. This is a bug where we cannot rename or delete a job through deployment. This bug happens when:
there are two or more jobs with the same name (but with different projects),
there are one or more jobs that use the duplicated name job mentioned in the first point as a dependency (like static dependency), and
when we want to re-deploy in the hope to rename the duplicate job names
To Reproduce
The following is just an example on how to reproduce this bug:
create two projects, let's name it projectA and projectB
create one job for each project above, let's name both of them jobA
deploy both of them
create another job under projectA, name it jobB and has jobA as the dependency
deploy the new job
try to rename jobA under projctB into jobA_b
deploy all jobs
what we get in database is that there are three jobs now, jobA for projectA, jobA for projectB, and jobA_b for projectB
Expected behavior
There should be only two jobs in the database, jobA for projectA and jobA_b for projectB and sensor should be created for jobB to point to jobA (not jobA_b).
The text was updated successfully, but these errors were encountered:
Describe the bug
This bug is highly related to another issue mentioned here. This is a bug where we cannot rename or delete a job through deployment. This bug happens when:
To Reproduce
The following is just an example on how to reproduce this bug:
projectA
andprojectB
jobA
projectA
, name itjobB
and hasjobA
as the dependencyjobA
underprojctB
intojobA_b
jobA
forprojectA
,jobA
forprojectB
, andjobA_b
forprojectB
Expected behavior
There should be only two jobs in the database,
jobA
forprojectA
andjobA_b
forprojectB
and sensor should be created forjobB
to point tojobA
(notjobA_b
).The text was updated successfully, but these errors were encountered: