Home

Jenkins connector for Team Channel - not working

%3CLINGO-SUB%20id%3D%22lingo-sub-101372%22%20slang%3D%22en-US%22%3EJenkins%20connector%20for%20Team%20Channel%20-%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-101372%22%20slang%3D%22en-US%22%3E%3CP%3ECurrently%20my%20Jenkins%20instance%20is%20not%20able%20to%20publish%20build%20results%20in%20the%20Team%20channel.%26nbsp%3B%20I%20have%20set%20up%20the%20Jenkins%20connector%20and%20have%20successfully%20added%20the%20connector%20plugin%20to%20my%20Jenkins%20instance.%26nbsp%3B%20Interstingly%2C%20it%20did%20publish%20the%20build%20results%20once%20for%20a%20recent%20build%2C%20but%20never%20again(or%20before).%26nbsp%3B%26nbsp%3B%20I%20don't%20beleive%20the%20problem%20is%20with%20teams%20because%20if%20I%20manually%20post%20a%20card%20to%20the%20team%20channel%20using%20cURL%3B%20I%20can%20successfully%20post%20a%20card%20to%20the%20channel.%26nbsp%3B%20In%20other%20words%2C%20this%20works%20on%20the%20command%20line%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecurl%20-k%20-H%20%22Content-Type%3A%20application%2Fjson%22%20-d%20%22%7B%5C%22text%5C%22%3A%26nbsp%3B%5C%22TESTING%5C%22%7D%22%20%3CWEBHOOK%20for%3D%22%22%20jenkins%3D%22%22%20connector%3D%22%22%3E%3C%2FWEBHOOK%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20works%20everytime%20regardless%20of%20the%20account%20and%20machine.%26nbsp%3B%26nbsp%3B%20So%20that%20rules%20out%2Fproxy%2Ffirewall%20issues.%26nbsp%3B%20The%20Jenkins%20logs%20have%20absolutely%20nothing%20useful.%26nbsp%3B%20Jenkins%20thinks%20everything%20went%20beautifully.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20my%20ask%20is%3A%26nbsp%3B%26nbsp%3B%20Are%20there%20any%20logs%20on%20the%20MS%20Teams%20side%20I%20can%20use%20diagnose%20the%20issue%3F%26nbsp%3B%26nbsp%3B%20My%20MS%20Teams%20administrators%20say%20they%20don't%20have%20access%20to%20any%20but%20we%20are%20new%20to%20Teams%2C%20so%20maybe%20we%20have%20overlooked%20something%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-101372%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320835%22%20slang%3D%22en-US%22%3ERe%3A%20Jenkins%20connector%20for%20Team%20Channel%20-%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320835%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%22Interstingly%2C%20it%20did%20publish%20the%20build%20results%20once%20for%20a%20recent%20build%2C%20but%20never%20again(or%20before).%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECould%20it%20be%20because%20your%20build%20has%20been%20failing%20several%20times%3F%20In%20that%20case%20you%20are%20just%20getting%20notified%20the%20first%20time%20it%20failed.%3CBR%20%2F%3ETo%20get%20notification%20every%26nbsp%3Bfailures%2C%20you%20need%20to%20tick%20the%20advanced%20option%20in%20Jenkins%20job%20configuraiton%20%3A%20%22Notify%20Repeated%20Failure%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHope%20this%20helps.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Currently my Jenkins instance is not able to publish build results in the Team channel.  I have set up the Jenkins connector and have successfully added the connector plugin to my Jenkins instance.  Interstingly, it did publish the build results once for a recent build, but never again(or before).   I don't beleive the problem is with teams because if I manually post a card to the team channel using cURL; I can successfully post a card to the channel.  In other words, this works on the command line:

 

curl -k -H "Content-Type: application/json" -d "{\"text\": \"TESTING\"}" <webhook for jenkins connector>

 

This works everytime regardless of the account and machine.   So that rules out/proxy/firewall issues.  The Jenkins logs have absolutely nothing useful.  Jenkins thinks everything went beautifully.

 

So my ask is:   Are there any logs on the MS Teams side I can use diagnose the issue?   My MS Teams administrators say they don't have access to any but we are new to Teams, so maybe we have overlooked something?  

1 Reply

"Interstingly, it did publish the build results once for a recent build, but never again(or before)."

 

Could it be because your build has been failing several times? In that case you are just getting notified the first time it failed.
To get notification every failures, you need to tick the advanced option in Jenkins job configuraiton : "Notify Repeated Failure"

 

Hope this helps.

Related Conversations