I hope somebody can help me with this issue.
I recently moved my azure pipeline approval release process from slack web hook to Azure pipeline App for slack, because I found that having the approve and reject button directly in slack chat was something really nice to have to make approvals easier.
This is the process I follow:
Install Azure pipeline App in slack workspace
Create a private channel and /invite #azpipelines
I signed in /azpipelines signing
Once those steps has been completed, I started to subscribe my release pipelines selecting the stages I was interesting in. Everything worked just fine for a couple of days, I was receiving the notifications and I was able to approve and reject them without any problem, which is great, but today, out of nowhere I realised that I was receiving the emails from azpipelines that a release has been issued but no notification in channel.
The documentation about azure pipeline is really poor and I have no idea what is going wrong with the configuration.
Did this happen to anyone before and can direct me on the right path of what could be the issue behind it?
Thank you very much for any help you can provide
Sometimes, I also could encounter the similar problems.
And many times, I can fix the issue via the following ways:
Unsubscribe and re-subscribe the notifications.
Log out and then log in again.
Uninstall and re-install the Azure Pipelines App.
May be you also can try this steps to see if the issue can be resolved.
Related
Any ideas on How to send "ephemeral" messages using Bot Framework Composer?
I am building a bot that "listens" in a shared channel and under certain circumstances, it should reply ONLY to a specific user. I know I could send a private message, but that will require the user to "get out" of the channel.
In Slack, it looks like this:
Ideas?
Thank you.
There is currently a bug in the C# BotFramework SDK's Slack adapter that, at present, blocks ephemeral messages from working. You can reference this GitHub issue that discusses the problem.
There is a workaround presented there, but it applies to the developer who is building his bot using the SDK. In your case, building from Composer, you could also clone the repo, make the necessary changes, and build the files locally. Then, you should be able to reference the updated library in the bot's runtime.
At this point, you ought to be able to construct an activity in Composer following the SDK's schema for a NewSlackMessage.
We've had a DevOps member leave recently and have had complaints that all of the integrations (incoming webhooks) that they had set up have stopped working... (once the user was disabled).
One suggestion for dealing with this was to notify the affected channels when we deactivate the user, but I can't find in the API methods a way to look up which channels a user might have configured these webhooks for...
Anyone had to do something like this?
To get the apps and internal integrations that have been installed by a specific user use the API method called team.integrationLogs.
This method lists the integration activity logs for a team, including
when integrations are added, modified and removed. This method can
only be called by Admins.
For a programmatic solution you will need to go through all log entries for one user / app to find out its latest status.
However, it might still become difficult to reinstall all that apps / setup all that webhooks again properly after a DevOps member has left depending on how good your documentation is. We have therefore started using a generic admin user (e.g. "slackadmin") as main installer for all important apps / integrations for our workspace.
I have an app which uses Parse and I want to migrate it to Firebase. I was extended the parse installation objects to send customized push notifications. I'm wondering if I can migrate these parse installation objects to Firebase and use it from Firebase.
There is no cookie cutter click-though way to import an app that uses Parse.com into Firebase. The products are too different for that.
There are however migration guides for developers looking to migrate their iOS and Android apps on the Firebase site: https://firebase.google.com/support/guides/#migrating_from_parse
There is also a repo with parse-migration-tools from Firebase: https://github.com/firebase/parse-migration-tools
Finally have a look at this question, where experienced developers chimed in already: How to migrate data from Parse.com to Firebase
[Disclaimer: Former lead of Parse Push. Author of parse-migration-tools]
I'm a bit nervous that you're out of luck if you're referring to "installation Ids". Firebase supports iOS and Android. Android devices aren't going to be easy to port for a few reasons, though iOS can be done without too much work. Let's break it down by the push backend:
Most people who talk about "installation Ids" are talking about Parse's self-hosted push network (PPNS or Parse Push Notification Service). This is hosted at push.parse.com and will go away in January. There's nothing anyone can do to keep those devices connected. As an FYI you'll also realy want to update your apps to disable PPNS because it will likely drain your customers' battery when they have a background service repeatedly trying to connect to a URI that isn't going to exist anymore.
If you're using GCM directly, you're still out of luck actually. Parse uses a version of GCM that's too old to work with Firebase. I tried to help fix it, but we weren't able to upgrade to GCM v4 and keep the Parse design style. The new Firebase SDK makes it possible to fix the issue and keep the Parse design requirements, but I'm far too overextended to build this right now. If someone wants to grab a shovel, I'd be glad to explain the right design.
iOS will actually work. I intended to make this turnkey in parse-migration-tools but won't have time until the end of the year. Firebase Cloud Messaging has a batchImport API for importing iOS tokens. I also wrote support for batchImport in parse-migration-tools to help you import your devices (and other data) faster. If I were migrating Parse Push from iOS, I would personally write a migration and bulkImport function that used batchImport to create GCM tokens and subscribed Parse Channels as FCM topics (note the batchAdd method; it may help you more efficiently do your initial import).
This should do the trick:
https://firebase.google.com/docs/cloud-messaging/ios/client#import_existing_user_apns_tokens
You can just importat all of the existing users device id's and FireBase will generate unique id's for them.
is there a way to setup Heroku to get a notification you when your config variables are updated?
thanks a lot
sorry for the very late reply, but I spoke with Heroku back then, and they said that it wasn't something that they did at the moment.
Very late to the party here, but just to give an updated answer. Heroku has support for webhooks so you can monitor those + more events on your end.
If you rather not build your own consumption pipeline, consider using LightFlare (I'm the creator) that has out of the box support of consuming Webhooks events from many services (heroku included) and notifies you at your choice(s) of destinations (slack / email etc ...).
LightFlare currently supports monitoring on services like:
Infra: GCP, AWS, Azure, heroku
Code/release: GitHub, bitbucket, netlify
Commerce: shopify, gumroad
More integrations based on our customers asks
I have a teamcity server configured for CI. Our svn connection occasionally drops, once this happens a project will no longer check for changes, but we are not warned about this without logging onto the servers' web page.
Is there a way to be notified when there is a VCS problem in Team City?
Do you use mail notification on you builds? If so, you can set it to be notified of "Build fails to start". There may be different reasons to fail, but for us, it is always losing connectivity to VCS server.
Subscribing to Notifications
Failed to Start Builds
I am not sure, but teamcity does have an extensive API and if I understand it right you should be able to get the information from that. I haven't used it yet, just tested it does work. Hope that may help!