Should I point out that a tool update will break our builds in the future?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
1
down vote
favorite
We have a build server at work that handles our software releases. It runs a particular version of the tools.
I have updated my tools and noticed that my builds were failing locally. I investigated this further and I know the problem is caused by one of the tools, but I wasn't able to find an easy solution even though I know the exact cause.
I have a fairly high work load right now, so I haven't said anything yet. I simply downgraded my own tools to match the build server. I am not looking to take on any extra work right now...
I know the build server will get updated eventually (could be months, could be hours, it is about a year behind the official releases right now). Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate? I am positive it will be dumped on me when it happens.
software-industry software-development
edited 11 hours ago
DarkCygnus
32.1k1362139
asked 11 hours ago
Catsunami
1607
add a comment |
up vote
1
down vote
favorite
We have a build server at work that handles our software releases. It runs a particular version of the tools.
I have updated my tools and noticed that my builds were failing locally. I investigated this further and I know the problem is caused by one of the tools, but I wasn't able to find an easy solution even though I know the exact cause.
I have a fairly high work load right now, so I haven't said anything yet. I simply downgraded my own tools to match the build server. I am not looking to take on any extra work right now...
I know the build server will get updated eventually (could be months, could be hours, it is about a year behind the official releases right now). Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate? I am positive it will be dumped on me when it happens.
software-industry software-development
edited 11 hours ago
DarkCygnus
32.1k1362139
asked 11 hours ago
Catsunami
1607
1
If it's dumped on you, you simply prioritize it against other tasks and provide work estimates like usual. There's no reason this should increase your weekly workload suddenly.
– Chris
10 hours ago
Who, if anyone, is responsible for the build server?
– Mawg
3 hours ago
Frankly speaking, if I would update the build server, notice this issue and spend significant time to evaluate the problem and you would tell me afterwards "Yeah, I've seen this issue a year ago on my machine, but I didn't say anything, because $reasons" I would be pretty mad at you. Add it to your issue tracker.
– Simon
2 hours ago
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
We have a build server at work that handles our software releases. It runs a particular version of the tools.
I have updated my tools and noticed that my builds were failing locally. I investigated this further and I know the problem is caused by one of the tools, but I wasn't able to find an easy solution even though I know the exact cause.
I have a fairly high work load right now, so I haven't said anything yet. I simply downgraded my own tools to match the build server. I am not looking to take on any extra work right now...
I know the build server will get updated eventually (could be months, could be hours, it is about a year behind the official releases right now). Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate? I am positive it will be dumped on me when it happens.
software-industry software-development
edited 11 hours ago
DarkCygnus
32.1k1362139
asked 11 hours ago
Catsunami
1607
We have a build server at work that handles our software releases. It runs a particular version of the tools.
I have updated my tools and noticed that my builds were failing locally. I investigated this further and I know the problem is caused by one of the tools, but I wasn't able to find an easy solution even though I know the exact cause.
I have a fairly high work load right now, so I haven't said anything yet. I simply downgraded my own tools to match the build server. I am not looking to take on any extra work right now...
I know the build server will get updated eventually (could be months, could be hours, it is about a year behind the official releases right now). Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate? I am positive it will be dumped on me when it happens.
software-industry software-development
software-industry software-development
edited 11 hours ago
DarkCygnus
32.1k1362139
asked 11 hours ago
Catsunami
1607
edited 11 hours ago
DarkCygnus
32.1k1362139
asked 11 hours ago
Catsunami
1607
edited 11 hours ago
DarkCygnus
32.1k1362139
edited 11 hours ago
DarkCygnus
32.1k1362139
edited 11 hours ago
DarkCygnus
32.1k1362139
32.1k1362139
asked 11 hours ago
Catsunami
1607
asked 11 hours ago
Catsunami
1607
asked 11 hours ago
Catsunami
1607
1607
1
If it's dumped on you, you simply prioritize it against other tasks and provide work estimates like usual. There's no reason this should increase your weekly workload suddenly.
– Chris
10 hours ago
Who, if anyone, is responsible for the build server?
– Mawg
3 hours ago
Frankly speaking, if I would update the build server, notice this issue and spend significant time to evaluate the problem and you would tell me afterwards "Yeah, I've seen this issue a year ago on my machine, but I didn't say anything, because $reasons" I would be pretty mad at you. Add it to your issue tracker.
– Simon
2 hours ago
add a comment |
1
If it's dumped on you, you simply prioritize it against other tasks and provide work estimates like usual. There's no reason this should increase your weekly workload suddenly.
– Chris
10 hours ago
Who, if anyone, is responsible for the build server?
– Mawg
3 hours ago
Frankly speaking, if I would update the build server, notice this issue and spend significant time to evaluate the problem and you would tell me afterwards "Yeah, I've seen this issue a year ago on my machine, but I didn't say anything, because $reasons" I would be pretty mad at you. Add it to your issue tracker.
– Simon
2 hours ago
1
1
If it's dumped on you, you simply prioritize it against other tasks and provide work estimates like usual. There's no reason this should increase your weekly workload suddenly.
– Chris
10 hours ago
If it's dumped on you, you simply prioritize it against other tasks and provide work estimates like usual. There's no reason this should increase your weekly workload suddenly.
– Chris
10 hours ago
Who, if anyone, is responsible for the build server?
– Mawg
3 hours ago
Who, if anyone, is responsible for the build server?
– Mawg
3 hours ago
Frankly speaking, if I would update the build server, notice this issue and spend significant time to evaluate the problem and you would tell me afterwards "Yeah, I've seen this issue a year ago on my machine, but I didn't say anything, because $reasons" I would be pretty mad at you. Add it to your issue tracker.
– Simon
2 hours ago
Frankly speaking, if I would update the build server, notice this issue and spend significant time to evaluate the problem and you would tell me afterwards "Yeah, I've seen this issue a year ago on my machine, but I didn't say anything, because $reasons" I would be pretty mad at you. Add it to your issue tracker.
– Simon
2 hours ago
add a comment |
4 Answers
4
active
oldest
votes
up vote
9
down vote
Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate?
It is always better to be proactive.
Even though you are full with tasks, you should inform this to your team leader or manager ASAP, so this can be taken care of.
By doing so, you could spare your whole team and company future issues and bugs that could come out. You could also spare them from monetary losses resulting from downtime due to the bugs.
Withholding this information is just a big trouble waiting to happen (and could backfire to you if you don't report it and it fails). Do inform about your findings, and document them if possible.
answered 11 hours ago
DarkCygnus
32.1k1362139
add a comment |
up vote
3
down vote
Should I point out that a tool update will break our builds in the
future?
Yes you should.
That way, your boss can find a way to remedy the situation, or defer the problem to later - perhaps by not updating the tools until there is sufficient free time to deal with the problem.
And if you are worried that something will be "dumped on you", then you just make sure to work with your boss to have them help decide what should come off your plate at that time.
answered 9 hours ago
Joe Strazzere
236k115691984
add a comment |
up vote
0
down vote
To put it simply, it's a bug. There's nothing exceptional to it. So register it in your bug tracker and continue with your assigned tasks. Let the organization unleash its full power (ahem) to handle it. When you work on it in future, don't see this alone as a bad sign: it could be that fixing bugs is your job.
(If your organization penalizes someone who files a bug, it's a wholly different topic. Similarly, if your organization doesn't help the devs to fix the bugs.)
answered 3 hours ago
kubanczyk
1,485913
add a comment |
up vote
-1
down vote
I am positive it will be dumped on me when it happens.
I would defer it until I have a solution, it always best to present a problem with a solution.
Unless I was solely responsible for the server in which case I would be controlling when the tool updates anyway. The main reasons I would defer it is that quite often tools with problems are fixed in the next update. This would solve my issue for me. Quite probably I would just resolve it and wouldn't even mention it as it is a fairly common issue with simple resolution strategies, no need for any drama.
If it did get dumped on me, my immediate solution would be to roll back to the old tools and contact the vendor for assistance.
answered 8 hours ago
Kilisi
106k59241418
1
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
add a comment |
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate?
It is always better to be proactive.
Even though you are full with tasks, you should inform this to your team leader or manager ASAP, so this can be taken care of.
By doing so, you could spare your whole team and company future issues and bugs that could come out. You could also spare them from monetary losses resulting from downtime due to the bugs.
Withholding this information is just a big trouble waiting to happen (and could backfire to you if you don't report it and it fails). Do inform about your findings, and document them if possible.
answered 11 hours ago
DarkCygnus
32.1k1362139
add a comment |
up vote
9
down vote
Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate?
It is always better to be proactive.
Even though you are full with tasks, you should inform this to your team leader or manager ASAP, so this can be taken care of.
By doing so, you could spare your whole team and company future issues and bugs that could come out. You could also spare them from monetary losses resulting from downtime due to the bugs.
Withholding this information is just a big trouble waiting to happen (and could backfire to you if you don't report it and it fails). Do inform about your findings, and document them if possible.
answered 11 hours ago
DarkCygnus
32.1k1362139
add a comment |
up vote
9
down vote
up vote
9
down vote
Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate?
It is always better to be proactive.
Even though you are full with tasks, you should inform this to your team leader or manager ASAP, so this can be taken care of.
By doing so, you could spare your whole team and company future issues and bugs that could come out. You could also spare them from monetary losses resulting from downtime due to the bugs.
Withholding this information is just a big trouble waiting to happen (and could backfire to you if you don't report it and it fails). Do inform about your findings, and document them if possible.
answered 11 hours ago
DarkCygnus
32.1k1362139
Should I just wait until the builds start to fail to deal with it, or be proactive and deal with it now even though it's just adding more work to my plate?
It is always better to be proactive.
Even though you are full with tasks, you should inform this to your team leader or manager ASAP, so this can be taken care of.
By doing so, you could spare your whole team and company future issues and bugs that could come out. You could also spare them from monetary losses resulting from downtime due to the bugs.
Withholding this information is just a big trouble waiting to happen (and could backfire to you if you don't report it and it fails). Do inform about your findings, and document them if possible.
answered 11 hours ago
DarkCygnus
32.1k1362139
edited 11 hours ago
answered 11 hours ago
DarkCygnus
32.1k1362139
answered 11 hours ago
DarkCygnus
32.1k1362139
answered 11 hours ago
DarkCygnus
32.1k1362139
32.1k1362139
add a comment |
add a comment |
up vote
3
down vote
Should I point out that a tool update will break our builds in the
future?
Yes you should.
That way, your boss can find a way to remedy the situation, or defer the problem to later - perhaps by not updating the tools until there is sufficient free time to deal with the problem.
And if you are worried that something will be "dumped on you", then you just make sure to work with your boss to have them help decide what should come off your plate at that time.
answered 9 hours ago
Joe Strazzere
236k115691984
add a comment |
up vote
3
down vote
Should I point out that a tool update will break our builds in the
future?
Yes you should.
That way, your boss can find a way to remedy the situation, or defer the problem to later - perhaps by not updating the tools until there is sufficient free time to deal with the problem.
And if you are worried that something will be "dumped on you", then you just make sure to work with your boss to have them help decide what should come off your plate at that time.
answered 9 hours ago
Joe Strazzere
236k115691984
add a comment |
up vote
3
down vote
up vote
3
down vote
Should I point out that a tool update will break our builds in the
future?
Yes you should.
That way, your boss can find a way to remedy the situation, or defer the problem to later - perhaps by not updating the tools until there is sufficient free time to deal with the problem.
And if you are worried that something will be "dumped on you", then you just make sure to work with your boss to have them help decide what should come off your plate at that time.
answered 9 hours ago
Joe Strazzere
236k115691984
Should I point out that a tool update will break our builds in the
future?
Yes you should.
That way, your boss can find a way to remedy the situation, or defer the problem to later - perhaps by not updating the tools until there is sufficient free time to deal with the problem.
And if you are worried that something will be "dumped on you", then you just make sure to work with your boss to have them help decide what should come off your plate at that time.
answered 9 hours ago
Joe Strazzere
236k115691984
answered 9 hours ago
Joe Strazzere
236k115691984
answered 9 hours ago
Joe Strazzere
236k115691984
answered 9 hours ago
Joe Strazzere
236k115691984
236k115691984
add a comment |
add a comment |
up vote
0
down vote
To put it simply, it's a bug. There's nothing exceptional to it. So register it in your bug tracker and continue with your assigned tasks. Let the organization unleash its full power (ahem) to handle it. When you work on it in future, don't see this alone as a bad sign: it could be that fixing bugs is your job.
(If your organization penalizes someone who files a bug, it's a wholly different topic. Similarly, if your organization doesn't help the devs to fix the bugs.)
answered 3 hours ago
kubanczyk
1,485913
add a comment |
up vote
0
down vote
To put it simply, it's a bug. There's nothing exceptional to it. So register it in your bug tracker and continue with your assigned tasks. Let the organization unleash its full power (ahem) to handle it. When you work on it in future, don't see this alone as a bad sign: it could be that fixing bugs is your job.
(If your organization penalizes someone who files a bug, it's a wholly different topic. Similarly, if your organization doesn't help the devs to fix the bugs.)
answered 3 hours ago
kubanczyk
1,485913
add a comment |
up vote
0
down vote
up vote
0
down vote
To put it simply, it's a bug. There's nothing exceptional to it. So register it in your bug tracker and continue with your assigned tasks. Let the organization unleash its full power (ahem) to handle it. When you work on it in future, don't see this alone as a bad sign: it could be that fixing bugs is your job.
(If your organization penalizes someone who files a bug, it's a wholly different topic. Similarly, if your organization doesn't help the devs to fix the bugs.)
answered 3 hours ago
kubanczyk
1,485913
To put it simply, it's a bug. There's nothing exceptional to it. So register it in your bug tracker and continue with your assigned tasks. Let the organization unleash its full power (ahem) to handle it. When you work on it in future, don't see this alone as a bad sign: it could be that fixing bugs is your job.
(If your organization penalizes someone who files a bug, it's a wholly different topic. Similarly, if your organization doesn't help the devs to fix the bugs.)
answered 3 hours ago
kubanczyk
1,485913
answered 3 hours ago
kubanczyk
1,485913
answered 3 hours ago
kubanczyk
1,485913
answered 3 hours ago
kubanczyk
1,485913
1,485913
add a comment |
add a comment |
up vote
-1
down vote
I am positive it will be dumped on me when it happens.
I would defer it until I have a solution, it always best to present a problem with a solution.
Unless I was solely responsible for the server in which case I would be controlling when the tool updates anyway. The main reasons I would defer it is that quite often tools with problems are fixed in the next update. This would solve my issue for me. Quite probably I would just resolve it and wouldn't even mention it as it is a fairly common issue with simple resolution strategies, no need for any drama.
If it did get dumped on me, my immediate solution would be to roll back to the old tools and contact the vendor for assistance.
answered 8 hours ago
Kilisi
106k59241418
1
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
add a comment |
up vote
-1
down vote
I am positive it will be dumped on me when it happens.
I would defer it until I have a solution, it always best to present a problem with a solution.
Unless I was solely responsible for the server in which case I would be controlling when the tool updates anyway. The main reasons I would defer it is that quite often tools with problems are fixed in the next update. This would solve my issue for me. Quite probably I would just resolve it and wouldn't even mention it as it is a fairly common issue with simple resolution strategies, no need for any drama.
If it did get dumped on me, my immediate solution would be to roll back to the old tools and contact the vendor for assistance.
answered 8 hours ago
Kilisi
106k59241418
1
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
add a comment |
up vote
-1
down vote
up vote
-1
down vote
I am positive it will be dumped on me when it happens.
I would defer it until I have a solution, it always best to present a problem with a solution.
Unless I was solely responsible for the server in which case I would be controlling when the tool updates anyway. The main reasons I would defer it is that quite often tools with problems are fixed in the next update. This would solve my issue for me. Quite probably I would just resolve it and wouldn't even mention it as it is a fairly common issue with simple resolution strategies, no need for any drama.
If it did get dumped on me, my immediate solution would be to roll back to the old tools and contact the vendor for assistance.
answered 8 hours ago
Kilisi
106k59241418
I am positive it will be dumped on me when it happens.
I would defer it until I have a solution, it always best to present a problem with a solution.
Unless I was solely responsible for the server in which case I would be controlling when the tool updates anyway. The main reasons I would defer it is that quite often tools with problems are fixed in the next update. This would solve my issue for me. Quite probably I would just resolve it and wouldn't even mention it as it is a fairly common issue with simple resolution strategies, no need for any drama.
If it did get dumped on me, my immediate solution would be to roll back to the old tools and contact the vendor for assistance.
answered 8 hours ago
Kilisi
106k59241418
answered 8 hours ago
Kilisi
106k59241418
answered 8 hours ago
Kilisi
106k59241418
answered 8 hours ago
Kilisi
106k59241418
106k59241418
1
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
add a comment |
1
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
1
1
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
This is absurd. Warning your colleagues to be careful not to update the server because doing so will break things is obviously the right and helpful thing to do, until there is a resolution available. Stop worrying about your own image of invincibility at the expense of success, and start giving consideration to what helps the overall effort you are employed to be a part of.
– Chris Stratton
6 hours ago
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f122694%2fshould-i-point-out-that-a-tool-update-will-break-our-builds-in-the-future%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
If it's dumped on you, you simply prioritize it against other tasks and provide work estimates like usual. There's no reason this should increase your weekly workload suddenly.
– Chris
10 hours ago
Who, if anyone, is responsible for the build server?
– Mawg
3 hours ago
Frankly speaking, if I would update the build server, notice this issue and spend significant time to evaluate the problem and you would tell me afterwards "Yeah, I've seen this issue a year ago on my machine, but I didn't say anything, because $reasons" I would be pretty mad at you. Add it to your issue tracker.
– Simon
2 hours ago